Hi alexanders58976719,Is Adobe Analytics implemented with first party
cookies?option 1: If it isn't, you could try to break down the mcvids
with browser to see if it's related to safari browsers only. If this is
not purely safari browsers but all over the place, then it might be
worth looking at this option: option 2: I have seen issues similar to
your one which was not related to any firstparty cookie issue, here we
saw that when users clicked through from one domain to another
subdomain, the ...
Hi paulr44860813,It makes sense that the visit count is higher when you
look break it down by tracking codes. A visit can easily have more than
one tracking code. Example: the user goes to google, searches for
product A, find your paid advertisement and click through to your
website, the tracking trigger campaign A in AA and registers 1 visit.
The user is not interested in the product and goes back to the google
search result page and searches again, not another paid ad shows up
which has campa...
Have you tried breaking the session refresh down by browser? I've seen
high numbers for cross domain tracking on Safari browsers (ITP and
blocking of cookies, especially 3rd party and cross domain) as they tend
to delete the mcvid when a user goes from domain A to B. The best way to
debug it, is to extract data from the data feed and then follow one of
the transaction ids that has session refresh and see on which page the
marketing channel was set to session refresh. You could look into this
If you have admin access to DTM, you can go to the preferred profile in
DTM, click the tab "Embed" (if you don't have it, it means you need to
find out who has access to this tab). Once you get access to this tab,
there will be another tab on the page that lists "FTP Delivery", that's
where all the ftp information will be. Waqas
Hello,I would recommend setting up a new evar that is tracking the
internal campaign tracking code, as you can control the expiry of that
evar as well. Another way of handling this could be to maybe look into
product finding method instead or addition to internal campaigns, as
this adds more value to your reporting. At the end of the day, you want
to see what functionality of your website works best and which internal
campaigns it can be be driven by. Have a look at this article that
Hello, It should work if you set the "scope" visit instead of hit. You
can't have more than 1 hit per event, so based on your screenshot, the
result will always be 0. If you set the scope to visit, that should
solve what you are trying to achieve.
Hi,Is it a SPA that the video is on? Might be worth running s.clearVars
once the event has fired with 25% to ensure that data is cleared before
the next request on 50% is made? haven't worked with Launch and Video
tracking, but sounds like that's the issue here. The event is staying
persistent. The s.clearVars() Function
I've installed Chrome canary (Googles developer version). For some
strange reason it bypasses some internal IT policies and actually allows
my browser to remember the extensions I have installed ( in the company
delivered chrome version all extensions are deleted every time you
restart your pc. Might be worth looking into it. )
Just tested and works fine for me. Try download Chrome Canary version
and then install the plugin. maybe your company policies are causing
some strange behavior for the plugin. Assuming you have tried to delete
and reinstall the plugin as well?
Hi DavidI can't access the domain:
hollywood.universalstudioshollywood.com.But it could be several things.
1. Do you have the marketing cloud visitor ID enabled on both domains?
2.Is the the cookiedomain period set to the same. (should be 2 in your
case)3. The namespace for the tracking is the same on both domains?4.
Are the trackingservers set to be the same across both domains?If you
are okay with it, you could share (or send in a PM) a screenshot of each
network request (one for the hollywood...
The contextData for mcvid doesn't exist as "out of the box". You need
your developers to set it to a custom contextData variable and then
parse that through to an evar with a processing rule. Kind regards,Waqas
Hi roshanc44331495, As I remember the code was setup inside a page load
rule (but it can be in a DCR or Event rule as well). The value is stored
in a cookie that you name yourself, and to get the actual value of the
cookie, you can just write "_satellite.readCookie('Name of your
cookie')". So inside DTM, in your "data element" you could retrieve the
value of the cookie and then use that value across your different tags.
In case you don't want the cookie to be stored for longer than after
Hi, In a data source file, you just set the products as you would do in
a web implementation. There a plenty of examples here: products on how
to set the product string. It's no different for a data source. If a
user buys multiple product at the same time, you send that as one line
as the transactionId for that user would be a unique ID. Have you
started by creating a template in data source?
And think this solves the question: Important: Google AdWords uses two
types of accounts: a) MCC (My Client Center) Account and b) Standard
Account. For this integration with Adobe Analytics, you must use a
Standard Account login, not an MCC Account login. The reason is that MCC
accounts act as an "umbrella" account that can access multiple AdWords
accounts with a single login, whereas the Standard account login can
access only one AdWords account per login.
Instead of using real time reporting to verify your implementation, you
should always do the following instead:1. Open your browser console
(Press F12)2. Go to "Network" tab3. Filter on "b/ss"4. Make sure
"preserve log" is ticked5. Load the url you want to debug. As Alexis
mentioned. It's most likely your implementation that is wrong and not
the real time report as it's just parsing through the data that is
hitting the Adobe Analytics servers. Good luck with the debugging.
Hi there,Try following these steps: Experience Cloud Help And also, the
benefits are that you will have your external data sources gathered in
analytics. which will make it easier to display impressions etc. in
adobe workspace, so your dashboard options will be more complete for the
end user (think of being able to display impressions for google adwords
and next to it your campaign data etc etc etc. ) Since there is no
"stitching" of the data you are uploading from Google Adwords to Adobe
Hi John, After your initial click on the first button, try calling
s.clearVars(); The s.clearVars() Function That would ensure that any
previous variables set are not associated with the next ones. Hope it
Hi there,Most likely your implementation that is not done correctly. All
other pages are most likely being tracked as "PageView". Have a look at
this documentation(or forward it to your implementation team): pageName
Hi Marion,I would set the value to prop. If the prop is being set on
every single hit (which it is as you mentioned), then you can easily
break it down by any success event anyways. Having a time variable in an
eVar is waste of eVar. As you can see in the documentation,
getTimeParting the method used is again a prop and not an eVar. /Waqas
Hi,You will most likely need to do the following:Go to the network tab
and filter for calls being made by the assets.adobedtm.com and look at
what scripts are taking so long to execute.Get access to your DTM,
allocate the tags (assuming it's due to a cookie look up code that is
causing delays) and see if you can replace it with a image tag instead
of JS. Normally you can reach out to the vendors/agencies of the tags
and have them send a image tag (pixel based solution) that you can use.
Hi Erik,That's not possible.You could make one version and then just
replicate the workspace out and change the report suite id and save as a
new one, if that's what you are after, but having multiple report suites
is not an option at the moment. Kind regards,Waqas
oh forgot to explain why it's happening... the redirect is happening
before the actual adobe analytics code is triggered on your page, so
your campaign code. The web analytics code fires on the redirected page,
but by that time the user doesnt have a campaign id in the url.