Purchase expiry sounds like a better option if the goal is to tie eVar
values to order IDs with as close to a one to one relationship as
possible. I suppose it would also depend on where the eVar is being
populated. If the value is populated only on the single hit wherein
purchaseID is passed, something like pageview expiration may be an
option as well. Ultimately the decision rides on business needs, but I
agree that visit expiration would cast too wide a net for your needs
here.Every variable ...
Purchase IDs are serialized, meaning each unique purchase is only ever
counted once. If ever passed again, the purchase is seen as a duplicate
and excluded from reporting (meaning only the first is ever counted).
I'm unsure why one would re-access the confirmation page, unless it were
to check on the reservation or booking. If that's the example you're
describing, I'm not entirely sure why any purchaseID would be passed
again without a purchase actually occurring. That said, if the same, now
Serialization of purchase ID occurs on a hit level. If a duplicate
purchase ID is detected, I would expect conversion variables and events
to be excluded from reporting for that particular hit. My guess in this
instance would be that the conversion variable is being set and
persisted in the variables "post" column at the time a separate
purchaseID is passed. To determine if this is the case, I would suggest
pulling a raw datafeed and filtering against post_eVar127 to determine
if this value is p...
The timeframe mentioned seems to coincide with Apple's ITP 2.1
announcement February 21st, though I'm not sure that this went into
effect immediately. I would only expect this to be an issue if these
were browser visits on the device as
It would be helpful to have a "last used" type of timestamp or something
similar on segments in order to be able to determine if a segment or set
of segments is in use or has ever been used to assist with making
decisions surrounding segment cleanup initiatives.
The Campaign Classic Data Connector (formerly Neolane) is able to export
segmented files for the purpose of remarketing to key visitors and
market populations based on dynamic marketing segments by returning
filtered data via the integration. To my knowledge, it doesn't share the
segment definition itself, however -- just the data file (similar to a
segmented DataWarehouse export).Adobe Campaign Key Benefits and Features
The screenshots provided allude to a need for Adobe Web Service Access
in order to integrate. Admin users have the ability to grant this level
of access. Once granted, your user account is assigned a web services
username and shared secret that, once again based on the screenshots of
the Datorama interface you've provided, can be plugged in to complete
the integration. I'd be interested to know if any links to documentation
were provided by Datorama to complete this third-party integration?
Mobile Attributes Dynamic Lookup files can be requested to be added to a
DataFeed through firstname.lastname@example.org. The file includes lookups for the
mobile_id column, which covers items such as screen dimension. If
enabled, the user_agent column cannot be included in the same feed.