Setting a goal to track successful form submits

[MelissaMa7]

I am trying to figure out how to setup a goal metric in the Reporting Settings area of Adobe Target for a successful form submit. If I use Conversion > Clicked Element, I can select the form submit button. However, this will include any time a user clicks the button even if it wasn't a successful submit. We use Google Analytics. So the event that fires when they click the submit button and it is successful is form_raq_success. I thought about using Pageviews and selecting the thank you page that loads after a successful submission, but I worry that won't be completely accurate if anyone reloads the page or accidently comes to the page. 

Is there anyway to set this up or get close to setting this up correctly?

[alexbishop · Accepted solution]

If it's possible (i.e. either via the tag manager config update or through a development request) you could add a Track Event call that happens based on the same trigger as that form_raq_success call. With this Track Event approach you send a named mbox (e.g. "formSubmit") and then within the Target reporting you specify the Goal Metric as Conversion --> Viewed an mbox --> formSubmit

You can give the mbox any name you want though, it doesn't have to be called formSubmit, that's just an example. There's full documentation here too 

[MelissaMa7]

Thank you! I will reach out to my development team to see if we can try this out. 

[KhushbooBh3]

Hi there,

I'm following up on the solution you provided and have a couple of questions regarding goal tracking in specific scenarios:

1. Tracking Goals on Separate Pages: I'm wondering if we need to explicitly include success pages (e.g., post-form submission) OR order confirmation pages in our A/B test setup, even when the activity itself is running on a different initial page.

   • For instance, consider a 5-step form. My current activity focuses on the first step, but the primary goal I'm tracking is the final "submit" button click on the fifth step.
   • Similarly, if we're running an activity on the homepage, but our goal is to track order confirmations that occur on a separate order confirmation page, should that page be included in the activity setup?

2. Best Practices for Including Success/Confirmation Pages: If the answer to the first question is yes, what would be the recommended approach? Directly adding the success page as an additional page in the A/B test seems problematic, as users could potentially land on it directly without interacting with the main activity page, thus skewing the results.

   Essentially, I'm trying to understand the optimal setup for an activity where content changes are limited to specific URLs, but goal tracking needs to encompass separate "downstream" pages that signify conversion.

Thanks in advance!