FAQ

Yes. The landing pages are where the click identifier is captured from the URL and written to a cookie. Installing it only on the confirmation page means the conversion is never attributed — with no visible error, just no record.

Yes, and it is a common way to install it. Global tag on All Pages, conversion tag on the purchase trigger. Confirm in GTM Preview that the value and identifier variables resolve — an empty variable is the most frequent cause of missing conversions in that setup. See platforms.

No. The tag is served by the platform and updates itself, within a 5-minute cache window. The only situation that requires a new tag is a change to the campaign identifier, which happens when you rename the campaign in the dashboard.

Yes, with the tag installed on both hosts. The tag tries to infer a cookie domain valid for both. If it cannot, set cookie_domain explicitly. See subdomain and cross-domain.

Cookies do not cross separate domains. Use Postback S2S, which does not depend on cookies, or propagate the click identifier in the URL and install the tag on the second domain as well.

Yes, with one caveat: conversion watching stays active for 120 seconds after the tag loads. If checkout can take longer than that, reload the tag on the confirmation route. See single-page applications.

Immediately. There is no propagation delay: as soon as the tag loads on a page with a valid campaign, tracking is live. What usually delays go-live is publishing on the client’s site and validating the test conversion.

The impact is negligible. It is ≈7 KB compressed, with no dependencies, loaded with defer — it does not block rendering. The requests it makes happen after the page paints. See requirements.

Partially. The tag is served from the platform’s domain and some blockers filter it by list. When that happens nothing is tracked — with no error on the page. To measure independently of the browser, use Postback S2S.

The advertiser’s page is unaffected. Every operation is wrapped in error handling and the configuration fetch has a 5-second timeout. An outage means conversions not recorded during that window — never a visible error or a broken layout.

No. Every cookie is first-party, written on the advertiser’s domain. Third-party cookie blocking in browsers does not affect attribution.

The platform is sending the value in cents. This happens often on Shopify, where checkout.total_price comes multiplied by 100. Divide by 100 before assigning it to the conversion object.

Yes. Reassign window.MoclickConversion with a different transaction_id. Every assignment is detected and processed.

Architecture and security covers layers, data flow, stored data, controls and limitations — enough for a security review and a vendor questionnaire. Supplementary documentation, including the internal route specification and the list of sub-processors, is provided to the contracting party under the contract.

No. They are estimates derived from clicks using market reference rates. The platform measures clicks and conversions; impressions and cost live on the media platform. Use both indicators as an order of magnitude only — for financial reconciliation, consult the delivery report. See indicators.

Different attribution models, conversion windows and time zones produce different counts for the same period. A divergence of 5% to 15% is normal in browser-side tracking. See divergence from the media platform.

30 days. For longer history, export the dashboard CSV periodically — a monthly export preserves the aggregate series.

It is current behavior: the By source and By campaign tables ignore the filter on their own dimension and always list every value. The cards and the By day table apply the filters normally — use those as your reference when checking totals.

The platform is built with practices that support compliance: first-party cookies, a hashed IP instead of the stored address, a parameter allowlist on input and limited retention. The specific legal framing — legal basis, need for consent, cookie notice — depends on the advertiser’s context and should be assessed with legal counsel. See Privacy and LGPD and Architecture and security.

No. What is stored is a SHA-256 hash of the IP combined with a site salt, used to distinguish events. The original address is never written and cannot be recovered from the hash.

It depends on the advertiser’s context — audience, jurisdiction, the legal basis adopted and the site’s policy. The platform does not decide that, and this documentation is not a substitute for legal assessment. If the site runs a consent platform, tag loading can be gated on the matching category.

The conversion may be forwarded to the media platforms contracted for the campaign, transmitting the click identifier, the transaction identifier and the value. The list of platforms involved in each campaign and the corresponding data processing agreements are provided to the contracting party under the contract, so they can feed the advertiser’s record of processing activities. See Privacy and LGPD.

Through the support channel, providing the click or transaction identifier tied to the order. Without one of those identifiers there is no way to locate the records, because we store no name, email or IP address in readable form.