Skip to content

Magento

Signals sends the order and checkout events your Magento store already emits to your advertising platforms from your server rather than from the shopper’s browser alone.

It covers both Magento Open Source and Adobe Commerce.

  • A Magento or Adobe Commerce site you can configure a connector against.
  • A registered domain whose DNS you can manage, since the subdomain step needs DNS records added. Any DNS provider works.

The subdomain is what makes tracking first party, and it has to exist before Magento can be set up. A project holds one subdomain, so if the project already has one you can skip this.

Enter a subdomain name, for example s2s or firstpartydata, and the domain of the site you are tracking. Studio pre-fills the domain from your work email, so check it is the right one, then click Next.

Studio then generates the DNS records. Add them at whichever provider manages your domain, either four NS records or a single CNAME depending on what you are given, then click Proceed and Finish. See Subdomain setup for the record types and the steps at each provider.

The subdomain has to sit under the main domain’s registry, and cannot be hosted as a primary domain in its own right. DNS changes take time to take effect, so a step that fails immediately after you add the records is worth retrying before investigating.

Once the subdomain is configured, complete the Magento connector setup in Studio, then connect a destination.

Personal identifiers are normalized and SHA-256 hashed before they are sent to any destination.

  • Complete the subdomain and confirm it resolves before touching the store. Everything else depends on it.
  • Use a staging store if you have one, so a misconfigured event does not distort live reporting.
  • Place a test order and confirm the events fire before judging the numbers.
  • Confirm the subdomain resolves before completing the connector setup. With NS records a partial delegation looks correct in the DNS panel and still fails.

The subdomain will not verify. The records are wrong or have not taken effect yet. Check they match what Studio showed, then wait before retrying. See Your subdomain is not resolving.

The connector setup completes but no events arrive. Check the subdomain resolves. With NS records a partial delegation looks correct in the DNS panel and still fails. See Your subdomain is not resolving.

It was working and stopped. A theme or plugin update may have removed the integration. Check it is still in place on the site.