Delta Between Adobe Analytics and Google DCM Floodlight Conversion Counts | Community
Skip to main content
J
jnqjd
Level 2
October 26, 2021
Solved

Delta Between Adobe Analytics and Google DCM Floodlight Conversion Counts

  • October 26, 2021
  • 1 reply
  • 3480 views

Hi, 

In Launch, we have a single page load rule setup to count conversion events in both Adobe and DCM.

When comparing Adobe Analytics data against the DCM click-based counts, we're seeing a delta of ~15%. 

 

*Additional details:

  • Adobe counts are higher than DCM counts
  • Launch Rule Details:
    • Event type = `Core - Window Loaded`
    • Condition set for data layer page name value
    • Actions: Adobe (set/send/clear) is set first followed by the DCM tag

I know this is within the "expected range" but I'd like to reduce this discrepancy if possible.

 

Question: does anyone have recommended methods for reducing deltas across Adobe and Google (DCM) systems?

 

(P.S. I realize we'll never get a 1:1 match and that comparing Adobe Analytics with DCM is far from apples-to-apples.)

Thank you in advance. 

 

*Updated to provide more detail

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Pablo_Childe

Sadly i don`t think it would help too much as users who block cookies affect the tracking at cookie/MID level. 

 

What is odd is that Adobe click counts are higher. I am wondering if you instead in Launch made a direct call rule then have your dev fire it as an on click event if that might make the numbers better aligned. Im thinking somehow on window load itself perhaps giving you some ghost results. Direct call rule is more specific which should make it cleaner.

1 reply

Pablo_Childe
Community Advisor
Pablo_ChildeCommunity Advisor
Community Advisor
October 27, 2021

I find some of the pixel based tracking cab be improved by actually by delaying the time the floodlight fires. This is best for page load events. Click events may not benefit as much from this technique.

 

Things like bots, users who dont allow the full pageload to occur before they leave, even cookie blockers can make this delta what you see today.

 

Make your launch rule only fire DCM pixels after 1 or 2 secs delay of user on page. This way some of the delta will reduce as well as you are likely to fire better pixel conversion on more human users vs bots/crawlers. 

 

Also some user agent filtering may help esp for linux types that could actually be crawlers. If user agent is something you are tagging and capturing not firing those for linux users could remove some of the delta as well.

 

Good luck

    J
    jnqjdAuthor
    Level 2
    October 28, 2021

    Thank you very much, @pablo_childe.

    I've added more detail above following your response (thank you for prompting that). 

     

    The issue is that the Adobe counts are higher than DCM (click-based) counts.

    Out of the examples you provided above, cookie blockers seem like the main issue type that'd cause this.

    In that event, would something as simple as updating the event type to 'window loaded' vs. 'library loaded' fix things?

     

    Thank you again.

    Please let me know if the extra info provided gives you any more ideas. 

    Pablo_Childe
    Community Advisor
    Pablo_ChildeCommunity AdvisorAccepted solution
    Community Advisor
    October 28, 2021

    Sadly i don`t think it would help too much as users who block cookies affect the tracking at cookie/MID level. 

     

    What is odd is that Adobe click counts are higher. I am wondering if you instead in Launch made a direct call rule then have your dev fire it as an on click event if that might make the numbers better aligned. Im thinking somehow on window load itself perhaps giving you some ghost results. Direct call rule is more specific which should make it cleaner.

      Terms & ConditionsAccessibility statement

      Loading footer...