How to send Experience Cloud Visitor ID to Analytics Extension in Launch?

[k_o123]

We're looking to start tracking unique visitors using the suggested Experience Cloud ID Service.

We've set this up in Launch but it appears in the network logs that only the organisation ID is being sent to the Analytics suite, and not the Experience Cloud Visitor ID.

We are using the Analytics extension in Launch, but all current documentation and threads refer to DTM, Appmeasurment or VisitorAPI.js.

Could somebody please clarify how we can configure the Experience Cloud Visitor ID to be sent to Analytics Extension in Launch?

Thank you.

 

[Pablo_Childe]

Just in your scode add a line like this:

/* Marketing Cloud ID */
s.eVarXX=_satellite.getVisitorId().getMarketingCloudVisitorID()

Where XX is your new evar defined for MID.

GLTU

[k_o123]

Thank you for your reply!

Is this directly in the Adobe Analytics extension config, or would I need to set up a new data element in Launch? 

[Pablo_Childe]

Depends on your scode config. If not then a data element could work. I have typically seen it in Launches Adobe Analytics module.

[yuhuisg · Accepted solution]

You don't have to use code at all!

1. Create a Data Element from the Experience Cloud ID Service extension > ECID. That data element returns the ECID Visitor ID.
2. In your Adobe Analytics "Set Variable" action(s), set your eVar(s) with that new data element.

[k_o123]

Amazing, thank you @yuhuisg  

For step 2, am I correct to assume that the "Set Variable" action is to occur inside a Rule? If so, what event do you recommend to trigger this Rule, and do you recommend to treat the data as a page view when "Sending a Becon"?

[yuhuisg]

Yes, the "Set Variable" action is inside a Rule. This can be a "global" rule that sets all of your required AA variables.

Alternatively, if you set your global variables inside the AA extension itself, then you can also set this eVar there.

[k_o123]

Thanks for the further clarification @yuhuisg!

Unfortunately this method doesn't seem to be working when I tried to implement it, I can't see the Experience Cloud ID parameter being sent in the Analytics request. Is there a specific eVar that I should be using?

Also, I can see in another example that the Organisation ID and Visitor ID are both included in the network request (see image below). However in my implementation only the Organisation ID is being set, but I don't remember setting this up. Could you advise on why this might be?

[yuhuisg]

I suspect that you haven't setup the Data Element and/or Rule correctly. You don't need to use a particular eVar, any eVar will do.

Can you please show screenshots of your Data Element and your Rule, including the Action where you're setting the eVar? Or if you're setting it in your AA extension itself, can you please show a screenshot of that setup?

[k_o123]

Thank you @yuhuisg 

Below are screenshots showing the data element and AA extension setup. I've set it to eVar3 as eVar1 and eVar2 are being used in a global rule for other data elements.

Data Element

Extension Setup

[yuhuisg]

Those screenshots look correct.

Are you able to share the website where this is happening?

[k_o123]

@yuhuisg The work is not published to production yet, but when reviewing the network logs I could not see the mid value being sent in any of the fields.

Does the ECID data element type capture the mid value for unique visitor tracking?

[yuhuisg]

Yes, the ECID data element type returns the mid value.

Since that still doesn't work, try using a dynamic variable instead. I.e. set your eVar3 to "D=mid". The "D=" instructs AA to copy the mid value into eVar3. So when checking your AA hits, if you see the mid value in the hits, then you can expect that in your AA reports, eVar3 will have that same mid value.

[takis]

Hi, I'm working with @k_o123 on the same task. 

It seems like the issue is that the mid value isn't being set at all, hence why these methods don't work. Can I check whether this is the right setup for the ECID extension?

[yuhuisg]

Oh, you've enabled Opt-in! In that case, the mid value will only get set when the user opts in to tracking. Check Adobe's documentation for configuring this, or you can refer to this blog too: https://webanalyticsfordevelopers.com/2021/02/16/consent-and-launch/

[k_o123]

Hey @yuhuisg , thanks for your suggestion

We've disabled 'Opt in' and also enabled the 'Pre Opt in Approvals' for ECID. However, this didn't work and we've received this error:

It's unusual because we can see in the logs that the Marketing Cloud Visitor ID is being obtained, but setting the data element to the ECID doesn't work.  

Could you please advise on why this might be?

[yuhuisg]

I've never seen that error before, so this is a new one to me.

In your browser console, run

_satellite.getVisitorId().getMarketingCloudVisitorID()

Does your mid value get returned?