- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
10-14-2021 02:01 AM
Crowdsourcing for wisdom on this one, especially from @Tealium staff.
With regard to using delayed actions (see article), I’m wondering if these can be triggered from HTTP API events, which are not a visit in the same way as a Collect tag event would be.
I have an asynchronous ‘finance approval’ event that could happen any between a handful of minutes to a couple of days of an in-session form-fill. However, to ensure accurate matching to data in a third-party system, I need to be able to add a minimum delay to ensure that records can be matched at the third-party‘s side (reducing connector errors).
To do this I’d like to use a delayed action to hold off on sending any data through until x minutes after the HTTP API event is received.
Solved! Go to Solution.
10-21-2021 05:46 AM
In AudienceStream, it doesn't matter what the source of a visit is - Collect tag, Collect API call, File Import - a visit is started for any of these inputs.
It's just that some of them don't enrich some of the built in attributes (for example Lifetime Visit Count isn't incremented by File Import).
However, all of these inputs will trigger a visit and therefore "In Audience at End of Visit" delayed connectors will fire as long as the visitor is in the audience at the end of the triggered visit.
10-21-2021 06:01 AM
Thanks, Mark. Exactly what I needed.
Copyright All Rights Reserved © 2008-2023