Month: March 2019

It is possible that  at 12:00 pm a person was located in a city and at 3:00 pm he was identified in another city (geo.city in target). He was connected by 4G.

It is possible that their IP can change. Adobe takes their IP and map it to a geo that is provided by geo-targeting vendor, Digital Element. The user’s ISP changed their IP address at some point.

Mobile device geotargeting on 4G, LTE, etc.  is less reliable than standard internet  (Cable, Fiber, etc.)

See from Digital Element’s accuracy FAQ here: https://www.digitalelement.com/resources/faq/

Yes. Generally, Internet traffic can be broken down by connectivity type into:

1) Wired PC-based traffic

2) WiFi-based mobile-device and PC traffic and

3) Cell tower-based mobile device traffic.

IP geolocation data will enable you to accurately target the first two connectivity types – fixed and Wi-Fi. In terms of traffic from mobile devices specifically, Wi-Fi connections represent well over 80 percent of mobile Internet device traffic in terms of how users are connecting, meaning most mobile device traffic can be accurately targeted using IP geolocation.

1. hashchange/single page application/ measuring multi-page application systems where the url does not change.
2. measuring in an angular environment using listener functionality
3. video milestone measurement using direct call rules.
4. AJAX calls
5. Fire direct call rule when object is not NULL
6. Firing event which is not available as event pre-set
7. Firing direct call rule from event base rule
8. In case of iFrame

Reference: https://www.digitalbalance.com.au/our-blog/how-to-use-direct-call-rules-in-dtm/

Go To: https://xyz.a.com/

Run This Code in browser Console:

var visitor = Visitor.getInstance(“[email protected]”);

destinationURLWithVisitorIDs = visitor.appendVisitorIDsTo(“https://xyz.newloanapp.com/apply”);

window.location = destinationURLWithVisitorIDs;

Takes me to https://xyz.newloanapp.com/apply with the appended MCID data.

_satellite.getVisitorId().getMarketingCloudVisitorID(); on both the https://xyz.a.com/ and https://xyz.newloanapp.com domainsto check if that match

Many variables contain limitations to the number of bytes they can hold. A byte is generally a single character, however can take up to 6 bytes depending on the complexity of the character. Any variables that exceed these limitations are truncated:

• PageName and all custom traffic variables (props): 100 bytes
• Tracking Codes and all custom conversion variables (eVars): 255 bytes
• URL and Referrer: 255 bytes
• Hierarchy variables: 255 bytes total across all levels
• The transactionID variable can contain any character other than a comma. It should be in the same location where the character limit (100 bytes) is specified. If multi-byte characters are used, multi-byte character support must be enabled in order to avoid problems with unexpected characters in the transactionID.
• Purchase ID: 20 bytes
• Products: 100 bytes for each product category
  100 bytes for each product name
  No overall limit within the entire variable
• Events variable: No overall limit, however each serialized value may only contain 20 bytes

On page load there will be s.t() server call ,on banner/image impressions there will be s.tl() server call so artificially it will depress bounce and bounce rate.

Here is the document that explains how each of these metrics works.

You can build a calculated metric using single access, but that will only work when looking at specific dimensions (pages, evars, etc.) and not from a site-wide perspective.  If you want something at the site level, then you can use single page visits.

You should use the metric that suits your need based on where/how they will use it in reporting.

Solution 1:

By the user of other metric we can solve this problem.

We can build a calculated metric using single access, but that will only work when looking at specific dimensions (pages, evars, etc.)

Single Page Visit / Entries

If you want something at the site level, then they can use single page visits.

Single Access / Visits

You should use the metric that suits the needs based on the requirement.

Solution 2:

Other solution to track banner ads is to populate the value of banner in local variable of javascript like banner1:banner2:banner3 and pass on that value to analytics variable like prop on page load. This can give insight that how many banner has been loaded at the time of page load.