--- title: "Tracking Domains" description: "A non-technical overview of Tracking Domains in RevCent, focused on how they enable first-party visitor tracking, conversion attribution, URL parameter metadata, ecommerce reporting, fraud context, and relationships to Tracking Visitor and Tracking Entry records." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/TrackingDomain.md" relationships: - name: "Tracking Visitor" url: "https://revcent.com/documentation/markdown/ecosystem/item/TrackingVisitor.md" - name: "Tracking Entry" url: "https://revcent.com/documentation/markdown/ecosystem/item/TrackingEntry.md" - name: "URL Parameter Set" url: "https://revcent.com/documentation/markdown/ecosystem/feature/URLParameterSet.md" technical_links: web_app: "https://kb.revcent.com/tracking/revcent-trackjs" api: section: "https://revcent.com/docs/api/v2#section-tracking" operations: - name: "Get Tracking Domains" operation_id: "GetTrackingDomains" operation: "https://revcent.com/docs/api/v2#operation-GetTrackingDomains" schema: "https://revcent.com/documentation/files/api/operation/GetTrackingDomains.json" - name: "Create A Tracking Domain" operation_id: "CreateTrackingDomain" operation: "https://revcent.com/docs/api/v2#operation-CreateTrackingDomain" schema: "https://revcent.com/documentation/files/api/operation/CreateTrackingDomain.json" - name: "Get A Tracking Domain" operation_id: "GetTrackingDomain" operation: "https://revcent.com/docs/api/v2#operation-GetTrackingDomain" schema: "https://revcent.com/documentation/files/api/operation/GetTrackingDomain.json" - name: "Edit A Tracking Domain" operation_id: "EditTrackingDomain" operation: "https://revcent.com/docs/api/v2#operation-EditTrackingDomain" schema: "https://revcent.com/documentation/files/api/operation/EditTrackingDomain.json" - name: "Initialize SSL for A Tracking Domain" operation_id: "InitializeTrackingDomainSSL" operation: "https://revcent.com/docs/api/v2#operation-InitializeTrackingDomainSSL" schema: "https://revcent.com/documentation/files/api/operation/InitializeTrackingDomainSSL.json" - name: "Initialize DNS for A Tracking Domain" operation_id: "InitializeTrackingDomainDNS" operation: "https://revcent.com/docs/api/v2#operation-InitializeTrackingDomainDNS" schema: "https://revcent.com/documentation/files/api/operation/InitializeTrackingDomainDNS.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewTrackingDomain.md" operations: - name: "Get Tracking Domains" operation_id: "GetTrackingDomains" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetTrackingDomains.md" available_via_ai: true - name: "Create A Tracking Domain" operation_id: "CreateTrackingDomain" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateTrackingDomain.md" available_via_ai: true - name: "Get A Tracking Domain" operation_id: "GetTrackingDomain" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetTrackingDomain.md" available_via_ai: true - name: "Edit A Tracking Domain" operation_id: "EditTrackingDomain" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditTrackingDomain.md" available_via_ai: true - name: "Initialize SSL for A Tracking Domain" operation_id: "InitializeTrackingDomainSSL" markdown: "https://revcent.com/documentation/markdown/mcp/operation/InitializeTrackingDomainSSL.md" available_via_ai: true - name: "Initialize DNS for A Tracking Domain" operation_id: "InitializeTrackingDomainDNS" markdown: "https://revcent.com/documentation/markdown/mcp/operation/InitializeTrackingDomainDNS.md" available_via_ai: true bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json" bigquery_tables: - "tracking_domain" --- # Tracking Domains Tracking Domains are RevCent features that allow a business to configure visitor and conversion tracking for domains it owns. They help connect website visits, landing-page activity, URL parameters, campaign data, and later ecommerce activity inside RevCent. In the RevCent ecosystem, a Tracking Domain is a configurable feature. Tracking Visitors and Tracking Entries are items that are created from tracking activity on configured domains. The purpose of this document is to explain the feature conceptually for LLMs, AI crawlers, and planning systems. It does not provide technical implementation instructions. For technical details, use the interface-specific links below. ## Technical Links by Interface | Interface | Use This When | Link | |---|---|---| | Web App | A human is learning about or configuring Tracking Domains, Track.js, DNS tracking, or visitor tracking through the RevCent web app and Knowledge Base. | [Web Knowledge Base](https://kb.revcent.com/tracking/revcent-trackjs) | | API | A developer is building a direct integration with RevCent tracking-domain operations. | [API Docs: Tracking](https://revcent.com/docs/api/v2#section-tracking) | | MCP / AI | An LLM, MCP client, or AI agent needs markdown-oriented guidance for understanding or working with the feature. | [MCP Markdown Overview](https://revcent.com/documentation/markdown/mcp/operation/OverviewTrackingDomain.md) | | BigQuery / Reporting | A data analyst, reporting workflow, or AI reporting agent needs schema details for analyzing Tracking Domain records. The primary table is `tracking_domain`. | [BigQuery Tables Schema](https://revcent.com/documentation/files/bigquery/dataset.json) | --- ## What Tracking Domains Are A Tracking Domain is a domain configured in RevCent so RevCent can track visitors and conversion activity for that domain. Tracking Domains support RevCent Track.js and DNS-based tracking. They give RevCent a known domain context for visitor tracking, URL parameter capture, conversion attribution, and fraud-related visitor context. Conceptually: ```text Tracking Domain ↓ Track.js or DNS tracking runs on the website ↓ Visitor activity is recorded ↓ Tracking Visitor and Tracking Entry records are created ↓ Visitor IDs and metadata can connect visits to sales or conversions ↓ Attribution, fraud context, and reporting become possible ``` A Tracking Domain should be understood as the configuration layer that allows RevCent to know which domain belongs to a merchant and how visitor tracking should work for that domain. ## Why Tracking Domains Are a Feature Tracking Domains are a feature because they are intentionally configured by the user. A business creates a Tracking Domain, identifies the domain to track, completes required setup such as DNS where applicable, and configures tracking behavior such as URL parameters or parameter sets. The Tracking Domain itself is not a visitor event. It is the configuration that enables visitor events to be collected. In the ecosystem model: ```text Tracking Domain = feature / configuration Tracking Visitor = item created from visitor identity Tracking Entry = item created from page-visit or tracking activity ``` This distinction matters because a Tracking Domain defines how tracking should happen, while Tracking Visitors and Tracking Entries preserve what actually happened. ## Core Purpose The core purpose of Tracking Domains is to make ecommerce visitor tracking and conversion attribution more reliable. Ecommerce businesses need to understand where purchases came from. A customer might arrive from an ad, an affiliate link, an email campaign, a social post, a search click, or a landing page. Tracking Domains help preserve that context so it can be connected to later purchases and business outcomes. Tracking Domains help answer questions such as: - Which campaign produced this sale? - Which traffic source generated revenue? - Which affiliate or sub ID should receive credit? - Which landing page converted best? - Which ad click became a customer? - Which traffic sources produced refunds, chargebacks, or fraud detections? - Which visitor path led to a subscription, trial, or repeat purchase? Without tracking domains and visitor attribution, that context may be lost before the purchase happens. ## Relationship to RevCent Track.js RevCent Track.js is the JavaScript tracking layer used with Tracking Domains. When Track.js is installed or enabled through a supported integration, it helps RevCent identify visitors and connect website activity to later ecommerce activity. This can include landing-page visits, URL parameter capture, session context, visitor identifiers, and conversion-related metadata. A Tracking Domain tells RevCent which domain should be tracked. Track.js collects the visitor activity on that domain. Conceptually: ```text Tracking Domain = where tracking is allowed and configured Track.js = script or tracking layer that captures visitor activity Tracking Visitor = visitor identity created from tracking Tracking Entry = individual tracking activity created from visits ``` ## Relationship to DNS Tracking Tracking Domains can use DNS-based tracking to improve first-party tracking reliability. DNS setup allows RevCent tracking to operate in a domain-specific way. This is important because modern browsers increasingly limit third-party cookies and cross-domain tracking behavior. With DNS tracking, the business can use domain-specific tracking infrastructure to preserve visitor identity more reliably. This matters for: - Conversion attribution. - Visitor identity continuity. - URL parameter persistence. - Sale-to-visitor matching. - Fraud context. - Analytics accuracy. - WooCommerce and custom storefront tracking. DNS setup is not just a technical checkbox. It affects whether tracking can work reliably enough for attribution and fraud analysis. ## First-Party Visitor Tracking Tracking Domains help RevCent support first-party visitor tracking. First-party tracking means visitor tracking is tied to a domain the merchant owns rather than relying only on generic third-party tracking behavior. This is valuable because first-party tracking is generally more compatible with modern browser restrictions and helps a business maintain a stronger connection between the visitor, the website session, and the eventual conversion. For ecommerce businesses, this can improve the accuracy of: - Marketing attribution. - Ad click attribution. - Affiliate attribution. - Landing-page performance. - Funnel performance. - Fraud review. - Customer journey analysis. ## Relationship to Tracking Visitors Tracking Visitors are items created from visitor identity on a configured Tracking Domain. A Tracking Visitor represents a visitor RevCent has identified or tracked. It can connect a person or browser session to tracking activity, metadata, and later ecommerce outcomes. The Tracking Domain enables this relationship by defining the domain where tracking is active. Conceptually: ```text Tracking Domain ↓ Visitor arrives on tracked website ↓ Tracking Visitor item is created or updated ↓ Visitor can later be associated with a sale, customer, fraud event, or conversion ``` Tracking Visitors are especially important because they help preserve continuity across multiple page views, sessions, or checkout steps. ## Relationship to Tracking Entries Tracking Entries are items created from individual tracking activity, such as page visits or tracked interactions. If Tracking Visitors represent the visitor identity, Tracking Entries represent the activity trail. A Tracking Domain provides the domain context for those entries. Conceptually: ```text Visitor lands on a tracked page ↓ Tracking Entry records the page or tracking event ↓ Tracking Entry belongs to the visitor and domain context ↓ Later reports can analyze paths, sources, and conversion activity ``` Tracking Entries help RevCent understand not just who visited, but what happened during the visit. ## Relationship to URL Parameters Tracking Domains can capture URL parameters and save them as metadata. URL parameters are commonly used by ad platforms, affiliates, and marketing campaigns to identify traffic source and campaign details. Common examples include: - `utm_source` - `utm_medium` - `utm_campaign` - `utm_content` - `utm_term` - `gclid` - `fbclid` - `ttclid` - `msclkid` - `affiliate_id` - `sub_id` - `click_id` - `campaign_id` - `ad_id` - `landing_page` When configured well, these values can become persistent metadata attached to the visitor and related commerce activity. This is one of the most important business uses of Tracking Domains because it turns anonymous ad-click and landing-page data into reportable RevCent metadata. ## Relationship to Metadata Tracking Domains help generate metadata that can later appear on visitors, sales, customers, or related commerce records. Metadata lets a business preserve business-specific context that is not part of the core object schema. For example: ```text utm_source = google utm_campaign = spring_sale gclid = ad_click_id affiliate_id = partner_123 sub_id = creative_a landing_page = skincare_v2 ``` This metadata can later be used for attribution, segmentation, reporting, fraud review, and AI analysis. Good metadata naming is important. Consistent names make later reports and AI workflows much easier to build. ## Relationship to Conversion Tracking Tracking Domains are foundational to RevCent conversion tracking. A conversion is meaningful only when RevCent can connect the purchase or business outcome back to the visitor and source context that produced it. Tracking Domains help support this connection by preserving visitor identity and metadata before the sale happens. A typical attribution path looks like this: ```text Visitor clicks ad or affiliate link ↓ Visitor lands on tracked domain with URL parameters ↓ Tracking Domain captures visitor and metadata ↓ Visitor reaches checkout or purchase flow ↓ Visitor ID is connected to the sale ↓ Sale can be analyzed by source, campaign, affiliate, or click ID ``` This makes Tracking Domains valuable not just for technical tracking, but for marketing and revenue analysis. ## Relationship to Sales Tracking Domains can help connect website visits to Sales. When visitor tracking is properly connected to a purchase request, the Sale can be associated with visitor context and metadata such as campaign, source, affiliate, or click ID. This helps the business understand which sales were produced by which marketing efforts. Tracking Domains are especially valuable when sales happen through: - WooCommerce stores. - RevCent-supported checkout flows. - Custom storefronts. - Landing pages. - API-created sales. - Affiliate-driven funnels. - Multi-domain ecommerce journeys. Without the visitor-to-sale link, a business may see the sale but lose the source context. ## Relationship to Customers Tracking Domains can help enrich the customer record indirectly. A customer may first appear as a visitor, then later become a buyer. When tracking and conversion linking are configured properly, the customer's origin context can be preserved through metadata and related tracking records. This helps answer lifecycle questions such as: - Which source created this customer? - Which campaign generated high-value customers? - Which affiliate produced repeat buyers? - Which landing page produced customers with high refund or chargeback rates? - Which traffic source led to subscriptions or trials? Tracking Domains help transform acquisition context into customer intelligence. ## Relationship to WooCommerce Tracking Domains are important for WooCommerce stores using RevCent. For WooCommerce, tracking can help connect storefront visitors to purchases created through the RevCent payment flow. DNS tracking may be enabled through the RevCent WordPress payment plugin when the tracking domain is set up for the same domain as the WordPress site. This helps WooCommerce merchants preserve attribution without needing every tracking detail to be manually handled in custom code. For WooCommerce businesses, Tracking Domains can support: - Visitor-to-order attribution. - Marketing source reporting. - Affiliate attribution. - Google Ads attribution. - Funnel analysis. - Fraud context for tracked visitors. - More complete ecommerce reporting. ## Relationship to Sentinel Anti-Fraud Tracking Domains can strengthen Sentinel Anti-Fraud by providing visitor context. Sentinel may use visitor-related data as part of fraud analysis. Tracking Domains help create the visitor records and tracking context that make that analysis more useful. For example, visitor context can help identify suspicious activity such as missing visitor data, proxy or datacenter behavior, repeated attempts, high-risk traffic sources, or unusual checkout paths. Conceptually: ```text Tracking Domain captures visitor context ↓ Tracking Visitor and Tracking Entry records preserve activity ↓ Sale or payment attempt occurs ↓ Sentinel can evaluate risk with better context ↓ Fraud Detection or alert may be created when fraud is detected ``` Tracking Domains are therefore part of both the attribution system and the fraud-prevention ecosystem. ## Relationship to Fraud Detections Tracking Domains can provide context for Fraud Detection records. When a Fraud Detection is created, visitor data, tracking entries, metadata, IP address, campaign source, or landing-page information can help explain what happened and why the event was risky. This is useful for: - Reviewing suspicious orders. - Understanding fraud sources. - Identifying risky traffic partners. - Comparing legitimate customers to suspicious visitors. - Investigating chargebacks. - Marking false positives accurately. - Improving future fraud prevention. A Fraud Detection without tracking context may show that fraud occurred. A Fraud Detection with tracking context can help explain where it came from. ## Relationship to Campaign and Affiliate Attribution Tracking Domains help connect campaigns and affiliates to downstream outcomes. This is especially useful for businesses that run paid ads, influencer campaigns, affiliate programs, media buying, or multi-channel marketing. URL parameters can identify traffic source, ad, affiliate, sub ID, creative, keyword, landing page, or campaign. Once that context is captured and connected to sales, the business can evaluate: - Revenue by source. - Refunds by campaign. - Chargebacks by affiliate. - Trial conversion by landing page. - Subscription retention by traffic source. - Average order value by ad creative. - Fraud detections by partner or campaign. Tracking Domains make these questions answerable because they help preserve the source data before it disappears. ## Relationship to Google Ads and Ad Click IDs Tracking Domains can help preserve ad click identifiers such as Google Ads `gclid`. A click ID is valuable only if it survives long enough to be connected to a conversion. Tracking Domains help preserve those values as metadata and make them available for reporting or conversion analysis. This is important for businesses that need to attribute sales back to paid ad platforms, campaigns, keywords, or ad clicks. The same concept can apply to other click identifiers such as `fbclid`, `ttclid`, `msclkid`, and generic affiliate click IDs. ## Relationship to AI Assistants AI Assistants can use Tracking Domain-related data to reason about marketing, attribution, conversion, fraud, and customer behavior. Examples include: - Summarizing which campaigns are producing sales. - Reviewing attribution metadata for a customer or sale. - Comparing conversion quality by traffic source. - Investigating suspicious traffic patterns. - Explaining why a sale has certain metadata. - Recommending URL parameters to capture. - Reviewing whether missing attribution may be caused by incomplete tracking setup. Tracking Domains provide the structured source context that makes this reasoning possible. ## Relationship to AI Voice Agents AI Voice Agents may use customer, sale, and tracking context during support or recovery conversations. For example, if a customer is associated with a tracked campaign or landing page, that context may help the business understand how the customer originally arrived or which store/funnel they used. AI Voice Agents should not expose internal tracking or fraud logic casually to customers, but the business may use tracking context internally to route support, understand customer history, or tailor follow-up workflows. ## Relationship to Functions Functions can use tracking-related events and metadata to automate downstream workflows. For example, a Function might send conversion context to an external analytics system, normalize metadata, notify a team about specific affiliate activity, or enrich a customer or sale workflow with tracking information. Tracking Domains are not the Function themselves. They create the visitor and metadata context that Functions can later use. ## Relationship to Email Templates Tracking metadata may influence Email Template logic or segmentation. For example, a business may want to send different internal notifications based on campaign source, affiliate, landing page, or attribution metadata. Customer-facing email should be handled carefully. Tracking and attribution data are usually internal business context, not information that needs to be exposed to the customer. ## Relationship to Reporting Tracking Domains are valuable for reporting because they preserve the domain-level configuration that produces visitor and conversion data. The `tracking_domain` BigQuery table can help identify configured tracking domains, including their names, domains, enabled status, and descriptions. Tracking Domain reporting is often combined with related tables such as Tracking Visitors, Tracking Entries, Sales, Customers, Transactions, Fraud Detections, Chargebacks, and metadata-bearing records. Useful reporting questions include: - Which tracking domains are active? - Which domains are tied to visitor and conversion activity? - Which domains generate the most visitors? - Which domains generate sales? - Which domains generate the highest-value customers? - Which domains generate fraud detections or chargebacks? - Which traffic parameters are producing revenue? - Which domains need better attribution setup? The Tracking Domain is the configuration anchor for this reporting. ## Relationship to BigQuery Tracking Domains are available in BigQuery through the `tracking_domain` table. That table is useful for reporting on configured domains and for joining domain configuration to visitor or conversion data when needed. Conceptually: ```text tracking_domain ↓ tracking_visitor ↓ tracking_entry ↓ sale / customer / fraud detection / conversion context ``` Because attribution often depends on metadata, reporting may also need to examine metadata arrays on related records. Tracking Domain reporting works best when URL parameters and metadata names are consistent across domains. ## Common Ecommerce Use Cases Tracking Domains support many ecommerce use cases: - Tracking visitors from landing page to purchase. - Preserving UTM parameters for reporting. - Preserving affiliate and sub ID values. - Associating ad click IDs with conversions. - Measuring campaign performance. - Comparing conversion quality by traffic source. - Understanding customer acquisition paths. - Supporting WooCommerce conversion tracking. - Improving fraud review with visitor context. - Supporting chargeback analysis by source. - Helping AI Assistants reason about attribution. - Building BigQuery reports by source, campaign, affiliate, or domain. ## Why This Matters in the RevCent Ecosystem Tracking Domains matter because they connect the pre-purchase journey to the commerce records inside RevCent. A sale is more useful when the business knows where it came from. A customer is more useful when the business understands how they were acquired. A fraud detection is more useful when the business knows which visitor, domain, IP, campaign, or traffic source produced it. Tracking Domains give RevCent a way to connect those pieces. They sit at the beginning of the ecommerce data chain: ```text Domain and traffic source ↓ Visitor activity ↓ Tracking metadata ↓ Sale or conversion ↓ Customer, revenue, fraud, retention, and reporting outcomes ``` This makes Tracking Domains foundational for attribution, analytics, and fraud context. ## Best-Fit Businesses Tracking Domains are especially valuable for businesses that: - Drive traffic from paid ads. - Use affiliates or media buyers. - Operate WooCommerce stores. - Use custom landing pages or funnels. - Need accurate conversion attribution. - Need to understand revenue by traffic source. - Need to track Google Ads or other click IDs. - Want better fraud context from visitor behavior. - Use multiple domains or storefronts. - Want BigQuery-based marketing and conversion reports. Even a small ecommerce business benefits from clean attribution because it helps identify which marketing spend is producing real revenue. ## Summary Tracking Domains are RevCent's configuration feature for domain-based visitor and conversion tracking. They allow a business to connect website visits, URL parameters, visitor identity, metadata, and eventual purchases inside the RevCent ecosystem. Tracking Domains relate closely to Tracking Visitors and Tracking Entries, which are the items created from visitor identity and page activity. They also support Sales, Customers, Fraud Detections, Sentinel Anti-Fraud, AI workflows, Functions, Email Templates, and BigQuery reporting. At a high level: ```text Tracking Domain = where tracking is configured Tracking Visitor = who visited Tracking Entry = what visit activity occurred Metadata = what source/campaign values were captured Sale or conversion = what business outcome happened ``` For technical setup, use the Web App, API, MCP, and BigQuery links in the header and technical links table. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.