Gomag Implementation Guide
DATA Reshape integrates with Gomag stores via the platform's tracking code injection points and DATA Reshape's first-party tracking subdomain. Full installation walkthrough coming soon.
Prerequisites
Only install after your custom domain and SSL certificate are active. The tracking subdomain (e.g. dre2.YOUR_DOMAIN.TLD) must share the same root domain as the storefront for cookies and CORS to work.
You will need:
- Custom tracking subdomain — e.g.
dre2.YOUR_DOMAIN.TLD - Script ID — provided by the DATA Reshape team
- Gomag API key — from your Gomag admin. Used to read order details server-side.
- Your order status list — see below. Required, and specific to your store.
Send us a screenshot or export of Comenzi → Stări Comenzi, including the numeric ID column.
Gomag does not send a dedicated event when an order is cancelled or refunded — those arrive as ordinary order saves, and the only thing that changes is the status. Without your list we cannot tell a completed sale from a cancellation, and refunds will never reach Google Ads or Meta, leaving reported revenue inflated by everything that gets returned.
The IDs are not the same across stores. They start from a shared core (1 new order, 2 phone order, 3 invoiced, 6 confirmed, 7 cancelled), but everything your team adds is store-specific — and even a shared ID can mean different things. On one store 5 is Returnata, an actual refund; on another it is Returnata (cerere de retur RMA), only the customer's request.
We especially need to know which statuses mean money actually went back to the customer. A return flow usually has several steps — form received, package in warehouse, under evaluation, approved for refund — and only the last one is a refund. Rejected returns (Retur Respins) must never trigger one.
You do not have to install everything by yourself. DATA Reshape provides hands-on implementation support and will perform the setup, audit, verification, and per-destination configuration on your Gomag store. To enable that, please create a dedicated Administrator account for us and email the credentials to [email protected].
- Role: Administrator (required to inject the tracking code, manage apps/integrations, and verify the install across page types).
- Recommended: create a fresh user (e.g.
datareshape) instead of sharing an existing one — easier to track activity and revoke. - Access can be revoked at any time once the installation and verification are confirmed live.
After access is granted, DATA Reshape will install the tracking code, audit and clean up duplicate destination code, adjust any conflicting integrations, and run the end-to-end verification — then report back when everything is live.
Verification
End-to-end verification is performed by the DATA Reshape team. Reach out at [email protected] or [email protected] once the tracking code is installed.
The tracking surface is built privacy-first: payloads are obfuscated, PII is normalized and hashed before it leaves the browser, sensitive parameters are encrypted at rest, identity is partitioned per account, and destination-specific protections (such as opt-out signals, data-minimization filters, and limited-use modes) are applied server-side before any downstream call.
Because of these advanced privacy and tracking protections, the data observable from the outside is intentionally not enough to validate quality on your own. DATA Reshape is the only party with the visibility needed to confirm that events, identifiers, conversions, and destination deliveries are correct end-to-end.