DoConure

Tracking, consent and the ad platforms

The public site (the home page, the legal pages, the contact form, the guide and /signup) can measure visits and campaigns. It is off until an id is set, and nothing leaves the visitor’s browser until they say yes. This page is for whoever runs the campaigns.

How it works

  • Consent, ours. A banner served from our own domain, in the page’s language (English or Italian), with Rifiuta tutto as prominent as Accetta tutto and a panel per purpose: necessary, statistics, advertising. The choice is kept six months in a first-party cookie; a link in every footer reopens it. Google Consent Mode v2 starts with every signal denied and is updated on the choice.
  • No request to a third party before a consent. The page reads one small file from its own domain (/tracking-config.json, public ids only) to learn which channels are on. If none is on — or the deployment is not production — there is no banner and no tag.
  • Each tag loads only for its purpose. Statistics: Google Analytics 4. Advertising: Google Ads, LinkedIn, OpenAI. With a Tag Manager container set, Tag Manager loads instead of gtag.js, after the consent defaults; the same events reach its dataLayer.
  • The app host carries nothing. The console, the admin, the signing pages and the verification page have no banner and no tag. /signup is the one public page on the app host.

The cookies and identifiers

NameSet byForLasts
doconure_consentus, the bannerremember the choice (version, statistics 0/1, advertising 0/1, time)6 months
sessionus, on the app host only (sign-in and the sign-up form)the console session and the forms’ anti-forgery token12 hours
_ga, _ga_*Google Analytics, after statisticstell visits apartper Google (up to 2 years)
_gcl_*Google Ads, after advertisingthe click that led hereper Google (90 days)
LinkedIn Insight cookiesLinkedIn, after advertisingcampaign measurementper LinkedIn
OpenAI pixel storageOpenAI, after advertisingcampaign measurementper OpenAI

Our own campaign record (the UTM labels, the landing page and the click id carried through the sign-up form) is separate and needs no cookie.

Setting it up

  1. In Settings > Tracking enter the public ids: ga4_measurement_id (G-..., one property for both sites), gtm_container_id (GTM-..., optional; it receives site_language in its dataLayer), google_ads_id (AW-...), linkedin_partner_id, openai_pixel_id. Each empty one is a channel that is off.
  2. Production sets TRACKING_ENABLED=1; staging and development never do, which is why no banner is offered and no tag loads there.

The events

Sent from the visitor’s browser, on the public pages only, after the consent; each carries site_language (it or en). None carries a name, an email, a phone number or anything typed.

EventWhenMark as key event in GA4
sign_upthe /signup form sent (the last step a browser sees)yes
generate_leadthe /contatti form sentyes
sign_up_start, contact_startthe first field touched in either form: with the two above, how many begin and how many finishno
cta_clicka click on any link to /signup (Get started, Inizia ora), with placement and pageno
pricing_viewthe price list openedno
docs_quickstart_viewa Quick Start of the guide opened (kind: document or signature)no
docs_searcha search in the guide, once the person stops typing: found yes or no — never the wordsno
language_switchthe language flag, with from and tono

Conversions of the ad platforms

  • Google Ads: the simplest way needs nothing here — mark sign_up and generate_lead as key events in GA4, link GA4 to Google Ads (both admin pages, once) and import them as conversions. For a direct Google Ads conversion instead, fill Google Ads conversions (direct): sign_up=AW-123456789/label, the send_to of each conversion (Goals > Conversions).
  • LinkedIn: in Campaign Manager create a conversion of type event-specific for each event you want, and fill LinkedIn conversions: sign_up=1234567,generate_lead=2345678. Needs the partner id.
  • OpenAI (ChatGPT Ads): OpenAI conversions lists which events the pixel measures (default sign_up,generate_lead). Needs the pixel id.

Each id is a public value (it is in the page anyway), so it lives in Settings, not in the environment: entered, it works at the next page load, with no deploy.

Testing with GA4 DebugView

Open the public site, accept statistics in the banner, and in Google Analytics open Admin > DebugView: your page views and events appear there. GA4’s Internal Traffic filter keeps your own visits out of the reports.

Nothing from the application

Since 1.5 the application sends no event to anybody: no conversion goes from our servers to Google, LinkedIn, OpenAI or any other platform, and nothing that happens in a console, on a signing page or through the API is shown to them. The application is measured by its own funnel and audit trail. Only the public site’s pages carry the tags above, behind the visitor’s consent. (Until 1.5 the Tracking page also validated server-side providers, exported a Google Ads offline-conversion CSV and excluded a browser: all three went with the server-side events.)