All good points.

I can segment for a hit using the hit scope in the segment builder. I'm trying to find the trend of what the page type is that people visit immediately after an event happens. But I want to know only the first value rather than all page types after the event.  I don't see how it is different to entr...

I'm trying to define a segment to get me the single hit after a particular event happens.  I've tried a number of combinations of sequential segments and exclusions but nothing seems to get just the one hit. The question I'm trying to answer is: What was the Page Type (v12 and p1) immediately after ...

 It looks like the cookieless hit isn’t included in the same visit.  So when the cookied hit brings back a new MCVID it is starting a new visit, rather than adding on to the anon session. We tested multiple visits from the same cookieless user, and Adobe was able to stitch them together into the rig...

Hello AA Experts! Has anyone implemented AA alongside One Trust for EU GDPR compliance?We have had it in place for a while, but recently had to make some updates that the legal team wanted to improve compliance.We put the Adobe optin code in the One Trust optanonwrapper function, setting the opt in ...

We want to serialize a numeric event so it is only captured once.  Is this possible? I can only find separate documentation about serialization and numeric types, but nothing about them together. If it is possible, what is the required syntax in the tag code? Assume our Event is XXX. We have 2 value...

I want to do a report on a particular product sku, but the calculated metric builder uses hit level segments which don't work with merchandising evars. Example:I want to know what percentage of sales are gift wrapping.  In Workspace I can add a filter on Product, which brings back the correct table....

It looks like this isn't a problem with the tag, but with the Chrome Extension.  The events are actually being fired each time. So I think it's not really a problem.

No, just a standard site.

We're doing testing having migrated from DTM to Launch.  Most things look right but there's something odd going on with the Facebook pixel. The tag is added via a rule, and then various events are triggered via additional rules based on either page load, or on button clicks.In Launch, it looks like ...