Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Adobe Analytics Data vs. Outbrain Data

verap3225836
Level 1
Level 1

Hello,

I have a question regarding the PageView data in Adobe analytics compared to the data I see in the advertising tool outbrain.

Outbrain tells me that I've had thousends of clicks on my banner ads wich lead to the campaign-URL with tracking parameters. When I search for these tracking-parameters in Adobe Analytics the tool tells me that there were only a fraction of pageviews for the period compared to outbrain.

For example:

In febuary I had an outbrain campaign with 1.469 clicks (according to outbrain).

Every URL had a tracking implemented.

Now I look up the campaign tracking in Adobe Analyitcs and there it says that the page with these utm-parameters were only visited 240 times.

Does someone has an idea what could be the problem? I'm pretty sure that there is no mistake in the way the Adobe tracking is implemented because compared with the data I get out of Google Ads there are only minimal differences.

Has anyone had similar experiences?

With kind regards

Vera

1 Accepted Solution
Alexis_Cazes_
Correct answer by
Community Advisor
Community Advisor

Check how your campaign variable is set up in terms or allocation and expiration as well.

If you capture the URL with query params in another dimension run it and you should be able to see how many time specific urls where loaded.

You might have some code issues that do not grab the query param for some reasons.

View solution in original post

1 Reply
Alexis_Cazes_
Correct answer by
Community Advisor
Community Advisor

Check how your campaign variable is set up in terms or allocation and expiration as well.

If you capture the URL with query params in another dimension run it and you should be able to see how many time specific urls where loaded.

You might have some code issues that do not grab the query param for some reasons.