With Signalize it is also possible to display notifications to visitors of AMP pages. This requires that the page be adjusted in a maximum of two places.
First, “amp-analytics” must be integrated. To do this, the corresponding script is loaded in HTML by adding a script-element in the head-element:
If several tracking tools are used simultaneously, the script only needs to be loaded once. Afterwards, the “amp-analytics” body element is integrated with the Signalize or etracker configuration:
<amp-analytics config="https://code.etracker.com/amp-config.json.php">
</amp-analytics>
In the code section above, “NU3bns” stands for the account key, which is uniquely assigned to each account.
Links on non-AMP pages
If the AMP pages contain links to non-AMP pages in the same domain, the following changes must be made:
- On the AMP page, assign additional attributes to all elements (hyperlinks) that refer to non-AMP pages (see below). These ensure that when the non-AMP page is called, additional URL parameters are sent along with it, which are transparently evaluated by the Signalize Code on the target page.
- On the target pages (non-AMP) the esSafeCrossDeviceeTracking.js is loaded immediately before (important before, not after!) the e.js:
This script makes sure that the information created by AMP-Analytics reaches Signalize.
Additional attributes for AMP to non-AMP hyperlinks
The following attributes must be inserted in exactly this form in elements in the AMP-HTML:
data-amp-addparams="et_cdi=CLIENT_ID(_et_amp_id)&et_ts=TIMESTAMP"
data-amp-replace="CLIENT_ID TIMESTAMP"
A link to the page https://non-amp.example.com from https://amp.example.com will look like this:
<a href="https://non-amp.example.com" data-amp-addparams="et_cdi=CLIENT_ID(_et_amp_id)&et_ts=TIMESTAMP" data-amp-replace="CLIENT_ID TIMESTAMP">Visit our traditional page</a>
