A4T Broken by Multiple Visitor Objects

[danieli73027437]

The Problem

We are running Adobe Test & Target on our own sites using A4T with no problems at all, we have a partner company that we white label a quote and by journey for. The setup is a little bit complex because we are running two Adobe Analytics Objects on the pages, one sending the data to our own report suite and one sending the data to our brand partners report suite. (separate organisation ID's)

A4T works by simply creating an SDID when Adobe Target, Analytics and Visitor Object are all present, this SDID will then by used to bind the data as the it's sent across to Adobe Analytics. The problem is because we have two Visitor Objects the SDID is never created and the data shows up as unspecified in Analytics. If we simply disable the second Visitor Object (the other companies one) the problem would be fixed. Unfortunately this can't be done because as a user click through from the other companies site and are passed to our own, they need to have their Visitor Object present otherwise when they are passed Analytics would class the user as a "new" user and the other companies visitor count would double because the journey would't be stitched.

Analytics Image Request (missing SDID)

Target Request (with SDID)

I have spend hour looking at this and have a ticket open with client care [Incident: 180514-000397] but as yet we havn't been able to find a valid solution, any help on this would be greatly appreciated.

Thanks

Dan

[settytb1]

Hi Dan,

When 2 Analytics objects are used it gets really messy very quickly. For that situation we recommend consulting to help in those situations.  Because all the code needs to be changed away from the s object, including any plugins, or below the line code, and attempting to use the same visitor object gets messy as well.  For the SDID specifically the target library creates the SDID and the Analytics library clears it when it fires.  So, it makes sense that the 2nd analytics library wouldn't see the SDID since the first one most likely cleared it as it fired.  This isn't a default use case that our code is really setup to support.  It would be something custom by consulting and I could see possible pitfalls that may make it just not work despite efforts to customize it.  Sorry, as this isn't the answer you are probably looking for but that specific situation with A4T isn't one that we included when designing the integration.

Not sure that helps,

Seth