Hello @jennifer_dungan ,
I think we would not want to alter the event to be participation based or linear based. But you are saying that even if we didn't define the attribution, we can simple make a segment that is "event 'x' exists" and apply tha to the table or panel? And then we can see all URL's in the rows and the metric as a column. Correct?
will this also work with cohort tables as well?
I think that would work if this is what you are saying (I will not be able to test this until a week or 2).
And to confirm, this will only work where you have defined a numbered event to occur. This will not work for manually created metrics correct?
Yes, I do segments like that frequently... where I will create a segment such as:
Visit Level
event x exists
OR
Visit Level
custom link equals "form x submitted" (you can create segments for each form separately for comparison)
OR
Visit Level
page contains "thank you"
Or whatever criteria I need to get all the pages back for visits that do "something"
(This will get me all the pages in the visit)
Or I will create Hit Level segments to pull out specific actions. (or some combination of these)
Note: Make sure that you test these out thoroughly to ensure that the data being returned really is what you expect... you don't want to mis-report this, then have to go back months later with corrections.
In your case, still having an explicit "Form Submit" event (on the form) will allow you to see what pages are submitting the form in the context of the visit...
Now for "CR" on your form, knowing which form is shown again will be easier if this is coded onto the page, rather than trying to calculate it... While not forms, we have "dialogues" that appear based on different criteria, so I can't just look at "Page X" and know that it has "dialogue A" - so I actually code in impression data (our developers tell me via data layers what is shown on the page) so that I can trigger contextual event data for "impressions".
So when I use my impressions metric, I can correlate to my URL to see how many times each dialogue is shown. I am also tracking the "CTA" clicks on these dialogues with another event.
This seems very similar to your form usage... now, because our site is complex with many different dialogues (and multiple dialogues per page), I actually use the s.product notation (using a unique category so that I can isolate my dialogues from other s.products values) but in this way, I can use a single impression event, a single click event, and use merchandising eVars to tell the dialogues apart along with their A/B/C etc variants (since I may have A variant for Dialogue X, and B Variant for Dialogue Y on the same page)
However, processing the data can get tricky due to the way Products works, but it means I can keep my variables and events minimized.
