You are on page 1of 9

Appier Web Tracking Code Integration Document

Version Update Content Date

1.0 Initial Version 2022/08/18


 
I.  About Document
The document is offered to Ancol.com for Appier Web Tracking Code integration.

II. Web Tracking Code Integration


NOTES:

The tag should trigger on the URLs regardless of the query string parameters.  For example, it
should trigger even if there is a different utm_source, utm_medium, or other parameters.

Installation via Tag Managers (e.g. GTM or Floodlight)


The "Tag Rule" trigger may not be the one your site uses.  In those cases, please use the
rule which best fits the description of the Tag Rule

The "Tag Name" is our recommended name for the tag; you may choose your own
naming convention

Installation via source code (for developers)

Please paste the code for each tag into the <head> tag of the relevant page.  Please
place the tag as high in <head> tag as possible.  
For further instructions for each individual tag, refer to the "Tag Rule/Code placement
details" section for each tag below.

Event List:
  Tag #1 Analytics
  Tag #2 Track Landing Page Tag

Tag #1 Analytics

Tag For all pages in the *.ancol.com domain, when the page loads, please trigger
Rule/Code the code below.
placement
details Example URLs:
https://www.ancol.com/

Note: The tag should trigger on the URLs regardless of querystring


parameters appended behind (e.g. should trigger even if there are different
UTMs/IDs etc).

Code <script>
window.appier_q = window.appier_q || [];
window.appier_q.push(
  {"t": "register", "content": { "id": "715e", "site": "ancol.com" }},
  {"t":"pv_track","action_id":
"PageView_9937","track_id":"e2e44bdf35c427e","isCountReload": true,"counter": 0},
   {"t":"pv_track","action_id":
"ViewTwoPages_9985","track_id":"e2e44bdf35c427e","isCountReload": false,"counter": 1})
</script>
<script src="//jscdn.appier.net/aa.js?id=ancol.com" async></script>

Tag #2 Track Landing Page Tag

Tag When the following URL loads, please trigger the code below.
Rule/Code
placement https://www.ancol.com/
details
Note:  The tag should trigger on the URLs regardless of querystring parameters
appended behind (e.g. should trigger even if there are different UTMs/IDs etc)

Code <script>
window.appier_q = window.appier_q || [];
window.appier_q.push(
  {"t": "register", "content": { "id": "715e", "site": "ancol.com" }},
  {"t": "type_landing", "action_id": "ViewLanding_4464", "track_id": "e2e44bdf35c427e",
"opts": {"unique_key": "true"}})
</script>
<script src="//jscdn.appier.net/aa.js?id=ancol.com" async></script>

III.  Others
Please feel free to contact us if you have any integration problems. (support@appier.com)

IV.  Testing process


(Testing process)How to make sure the tag has triggered or not
1.  How to make sure the Tag #1 Analytics triggered or not
[The testing process]
Step 1: Open "Chrome Developer Tools" ( Press F12 or Ctrl+Shift+I )
 Reference: https://developer.chrome.com/devtools
 

Step 2: Choose "Network Panel"

Step 3: Input filter "aa.js" to filter, in order to make sure the page already loaded the Appier JavaScript library
"aa.js".

 
2.  How to make sure the Tag #2 Track Landing Page triggered or not
[The testing process]
Step 1: Open "Chrome Developer Tools" ( Press F12 or Ctrl+Shift+I )
Step 2: Choose "Network Panel" and also check the "Preserve log" checkbox.
Step 3: Input filter "t0.c.appier.net" to filter, and access the landing page, then see if the tag triggered or not

3.  How to make sure the other tags have triggered correctly or not.
[The testing process]
Step 1: Open "Chrome Developer Tools" ( Press F12 or Ctrl+Shift+I )
Step 2: Choose "Network Panel" and also check the "Preserve log" checkbox.
Step 3: Input filter "t0.c.appier.net" to filter, and then execute the action, then see if the tag triggered or not
Step 4:Switch to “Payload” Panel and check if action_id is correct as code document
Step 5: Input filter  "type_process" or  "type_conversion" to filter, then execute the action, then see if the Tag
executed or not
(FAQ)Why didn’t the Tag trigger
Common cases and things to check below:
● The testing process didn’t match the requirements set in the Code Placement
Details section.
● Please check if the Tag implemented wrong, for example, tag is inside a
conditional if( my_condition ){...} doesn’t pass.
● The format of Appier Tag is wrong.
● May be caused by human error when copy-pasting wrongly, for example,
losing one quotation mark or bracket.  Please check the Developer Tools
Console tab for JavaScript errors.
● During the testing process, when input the keyword to filter, there’s a typo in
keyword:
● Example: typo with "type-home" when it is actually "type_home".
● Example: typo with "to." when it is actually "t0."

You might also like