Adobe Experience Platform Data Collection

Marian891210 · 4/20/22

Hello! I'm facing an issue when trying to send pageviews in Adobe Analytics. The rule is setup like in the following screenshot:

and here are the logs within the developer console:

but in the Adobe Experience Cloud debugger there is no Analytics request:

In the Network tab there are only Target requests.

Can you please help me find out why this may happen?

(I'm working on a test environment with the staging code deployed and it is limited by IP so I can't share the website url)

Thanks a lot!

Marian891210 · 5/4/22

Hi all! I managed to find out why the request was not being sent. It seems that the "Experience Cloud ID Service" extension had the "Opt in?" feature set to "Yes". After I changed this to "No" I managed to send the Adobe Analytics request.

Thank you all for all your time and responses!

View solution in original post

Gokul_Agiwal · 4/21/22

Hi @Marian891210

It seems like there might be issues with Rule ordering. I can see from your logs firing page view beacon action fired first and then your dom ready rule. It should be other way round.

For reference I've setup something similar like yours and the rule firing as expected.

Hope this helps.

Marian891210 · 4/21/22

Thank you very much @Gokul_Agiwal! I appreciate you took some time to answer to my question.

I noticed that my Actions were set to "WAIT, THEN" but in your screenshot were set to only "THEN". I changed this by unchecking the "Wait to run next action" from the "Advanced options" section within the "Adobe Analytics - Set Variables" action.

But it seems that the output is still the same, the beacon is firing first and afterwards the Dom Ready rule is firing:

Do you have any other ideas of why this is not working properly? Thank you!

yuhuisg · 4/21/22

Do you see any errors in your browser console?

Marian891210 · 4/21/22

Hi, @yuhuisg!

Only one in regards to a favicon connection and two warnings:

Thank you!

yuhuisg · 4/21/22

I think the "Wait to run next action" shouldn't be a factor in the problem.

If you use another Core event, e.g. Library Loaded or Window Loaded, do you get the same problem?

Gokul_Agiwal · 4/21/22

Hi @Marian891210

Yes can you try other events and checked - if the same problem occur. Agree with @yuhuisg about "Wait to run next action" is not a problem.

I've setup the test rule like below and can see the analytics request firing correctly in debugger also in browser's network tab. use b/ss for filter the result in network tab,

Marian891210 · 4/21/22

@Gokul_Agiwal I filtered the requests by "b/ss" but there are none in the Network tab:

May this be the problem? Do you have any idea of how can this be fixed?

Thank you!

Marian891210 · 4/21/22

@yuhuisg I tried Library Loaded and Window Loaded but the output is the same, no pageview hit in the Adobe Experience Cloud Debugger...

Gokul_Agiwal · 4/21/22

Hi @Marian891210 - If none of the events are working and if you can't see analytics request in network tab then I suspect there might be issues with your Analytics extension setup.

Can you please check the analytics extension configuration is correct? tracker globally accessible so you can able to see s object in browser console.

Marian891210 · 4/26/22

Hi, @Gokul_Agiwal!

I checked again the configuration but everything it seems to be properly set up.

Here are some screenshots from the Adobe Analytics Extension configuration:

(no custom code is added)

Maybe you can spot something that may cause this issue.

Thank you very much for your help!

yuhuisg · 4/26/22

You didn't specify any SSL tracking server. I don't think that will break AA tracking, but that field really should be filled in, especially if your website requires secure HTTPS connections.

Check your domain periods. Is your website www.website.com or www.website.co.uk or something else? If www.website.com, then yes, it should have 2 domain periods. If it's www.website.co.uk, then it should have 3 domain periods. See https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/cookiedomainperiod...and https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/fpcookiedomainperi....

Gokul_Agiwal · 4/26/22

Hi @Marian891210

Rightly spotted by @yuhuisg - Looks like you missed the SSL tracking server configuration and domain periods.

Marian891210 · 4/27/22

Hi, @Gokul_Agiwal! Thank you for validating @yuhuisg's point.

Marian891210 · 4/27/22

Thank you @yuhuisg!

If the tracking server is something like xyz.tt.omtrdc.net then the SSL tracking server should be xyz.ssl.tt.omtrdc.net, is that right? Because I tested with xyz.ssl.tt.omtrdc.net and it still doesn't work.

In regards to the domains period, my website is www.website.com, so I think it's ok I set 2.

Gokul_Agiwal · 4/27/22

Hi @Marian891210

The tracking server value depends on if you use first party cookies or third party cookies.

Adobe recommendation is to use first part cookies in your implementation.

Below links will help you to setup the tracking server and its details please go through it.

Tracking Server

First Party cookies

Hope this helps.

Marian891210 · 4/27/22

Hi @Gokul_Agiwal!

We are using third party cookies since the tracking server domain is ending in omtrdc.net on staging and in 207.net on production.

From AA documentation:
Your organization may already be using a 3rd party tracking server in the sc.omtrdc.net or 2o7.net domains. These were primarily used in previous versions of Adobe Analytics and are still valid.

I think I hit a dead end, no matter what SSL tracking server I'm adding, the result is the same > no hit is sent to AA.

Thank you very much for all your support!

yuhuisg · 4/27/22

What browser are you using? Do you have any extensions that block marketing / ad tracking?

Is anyone else facing the same problem as you?

Marian891210 · 4/28/22

Hi @yuhuisg!

I'm using Chrome Version 100.0.4896.127 (Official Build) (x86_64) and I have no extension that can prevent Launch from triggering, no ad blocking or tracking blocker.

I am not aware of anyone else with the same problem.

yuhuisg · 4/28/22

Can you share the website please?

Also, if no one else has the same problem, then… well… the problem might lie with something in your browser and/or computer. Have you tried with another browser and/or a private window?