--- title: "URL Parameter Sets" description: "A non-technical overview of URL Parameter Sets in RevCent, focused on reusable visitor URL parameter capture, Tracking Domain association, Metadata creation, Tracking Visitor persistence, and conversion attribution setup." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/URLParameterSet.md" relationships: - name: "Tracking Domain" url: "https://revcent.com/documentation/markdown/ecosystem/feature/TrackingDomain.md" - name: "Metadata" url: "https://revcent.com/documentation/markdown/ecosystem/feature/Metadata.md" - name: "Tracking Visitor" url: "https://revcent.com/documentation/markdown/ecosystem/item/TrackingVisitor.md" technical_links: web_app: "https://kb.revcent.com/en/tracking/url-parameter-set" api: section: "https://revcent.com/docs/api/v2#section-tracking" operations: - name: "Get URL Parameter Sets" operation_id: "GetUrlParameterSets" operation: "https://revcent.com/docs/api/v2#operation-GetUrlParameterSets" schema: "https://revcent.com/documentation/files/api/operation/GetUrlParameterSets.json" - name: "Create A URL Parameter Set" operation_id: "CreateUrlParameterSet" operation: "https://revcent.com/docs/api/v2#operation-CreateUrlParameterSet" schema: "https://revcent.com/documentation/files/api/operation/CreateUrlParameterSet.json" - name: "Get A URL Parameter Set" operation_id: "GetUrlParameterSet" operation: "https://revcent.com/docs/api/v2#operation-GetUrlParameterSet" schema: "https://revcent.com/documentation/files/api/operation/GetUrlParameterSet.json" - name: "Edit A URL Parameter Set" operation_id: "EditUrlParameterSet" operation: "https://revcent.com/docs/api/v2#operation-EditUrlParameterSet" schema: "https://revcent.com/documentation/files/api/operation/EditUrlParameterSet.json" - name: "Delete A URL Parameter Set" operation_id: "DeleteUrlParameterSet" operation: "https://revcent.com/docs/api/v2#operation-DeleteUrlParameterSet" schema: "https://revcent.com/documentation/files/api/operation/DeleteUrlParameterSet.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewUrlParameterSet.md" operations: - name: "Get URL Parameter Sets" operation_id: "GetUrlParameterSets" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetUrlParameterSets.md" available_via_ai: true - name: "Create A URL Parameter Set" operation_id: "CreateUrlParameterSet" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateUrlParameterSet.md" available_via_ai: true - name: "Get A URL Parameter Set" operation_id: "GetUrlParameterSet" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetUrlParameterSet.md" available_via_ai: true - name: "Edit A URL Parameter Set" operation_id: "EditUrlParameterSet" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditUrlParameterSet.md" available_via_ai: true - name: "Delete A URL Parameter Set" operation_id: "DeleteUrlParameterSet" markdown: "https://revcent.com/documentation/markdown/mcp/operation/DeleteUrlParameterSet.md" available_via_ai: true --- # URL Parameter Sets URL Parameter Sets are the RevCent feature used to define reusable groups of URL query parameters that RevCent should capture from tracked visitors. A URL Parameter Set is not a Tracking Visitor and is not Metadata by itself. It is configuration that tells RevCent which URL parameters matter when a visitor lands on a tracked site. The practical idea is: ```text URL Parameter Set = reusable list of URL parameters to capture Tracking Domain = domain where RevCent tracking runs Tracking Visitor = visitor record that can preserve captured parameter values Metadata = name/value context created from captured parameters ``` URL Parameter Sets are especially useful when a business has multiple domains, multiple campaigns, affiliate links, paid traffic links, or custom landing page parameters that should be preserved consistently. --- ## Why URL Parameter Sets Are a Feature URL Parameter Sets are a feature because they are reusable account-level tracking configuration. A business can create one URL Parameter Set and attach it to one or more Tracking Domains. This avoids manually configuring the same parameter list on every domain. Conceptually: ```text Business creates URL Parameter Set ↓ Business adds URL parameters to capture ↓ Business attaches the set to one or more Tracking Domains ↓ A visitor lands on a tracked domain with matching query parameters ↓ RevCent captures matching values ↓ Captured values can become Metadata associated with the visitor and later purchase activity ``` This makes URL Parameter Sets different from the captured Metadata itself. The set defines what to look for; Metadata is the saved name/value context that results from visitor and purchase activity. --- ## Technical Links | Area | Link | |---|---| | Web App | `https://kb.revcent.com/en/tracking/url-parameter-set` | | API | `https://revcent.com/docs/api/v2#section-tracking` | | MCP | `https://revcent.com/documentation/markdown/mcp/operation/OverviewUrlParameterSet.md` | --- ## Core Purpose The core purpose of a URL Parameter Set is to answer: ```text Which URL query parameters should RevCent capture from visitors on tracked domains? ``` Common examples include: ```text utm_source utm_medium utm_campaign utm_content utm_term gclid fbclid ttclid msclkid affiliate_id sub_id click_id ad_id adset_id creative_id landing_page checkout_page ``` If a visitor lands on a tracked domain with a URL such as: ```text https://example.com/landing-page?utm_source=google&utm_campaign=spring_sale&affiliate_id=partner_123 ``` and the attached URL Parameter Set includes those parameters, RevCent can capture the values and preserve them as visitor context. --- ## Relationship to Tracking Domains A URL Parameter Set must be associated with a Tracking Domain before it affects that domain's visitor tracking. Creating the URL Parameter Set alone does not automatically make a Tracking Domain use it. The relationship is: ```text Tracking Domain uses one or more URL Parameter Sets URL Parameter Set defines parameter names to capture Visitor URL provides values RevCent stores matching values for the tracked visitor ``` In API/MCP terms, the URL Parameter Set can be associated with a Tracking Domain through the Tracking Domain configuration, commonly by editing the Tracking Domain's `url_parameter_sets` array. Safe workflow: ```text Create or retrieve URL Parameter Set ↓ Retrieve the Tracking Domain ↓ Attach the URL Parameter Set to the Tracking Domain ↓ Verify the Tracking Domain includes the intended set ↓ Test a visitor URL containing expected parameters ``` --- ## Relationship to Tracking Visitors Tracking Visitors are the visitor records that allow RevCent to connect browsing activity to later purchase activity. URL Parameter Sets help Tracking Visitors preserve origin context. For example: ```text Visitor arrives with ?utm_source=facebook ↓ Tracking Domain recognizes visitor ↓ URL Parameter Set says utm_source should be captured ↓ Tracking Visitor can retain that value for the configured duration ↓ Later purchase activity can receive the captured context ``` This is why URL Parameter Sets are important for multi-page and multi-domain funnels. The visitor may land on one page, navigate across several pages, and purchase later. The Tracking Visitor is the bridge that helps preserve the captured context. --- ## Relationship to Metadata URL Parameter Sets are one of the main ways Metadata is created from visitor traffic. When RevCent captures a configured URL parameter, the captured parameter can become a Metadata entry. For example: ```text URL parameter: utm_campaign Captured value: spring_sale Saved Metadata: utm_campaign = spring_sale ``` or, when a custom saved name is configured: ```text URL parameter: utm_source Saved Metadata name: source Captured value: google Saved Metadata: source = google ``` URL Parameter Sets should be designed with consistent Metadata names because those names become durable context attached to visitor and purchase records. --- ## Automatic Purchase-Time Metadata vs Manual InsertMetadata URL Parameter Sets participate in the automatic visitor-tracking path. During an initial purchase, metadata captured from the visitor journey can be automatically attached or propagated to related purchase records, such as the Sale, Customer, Transaction, Shipping, and other related items created by that purchase context. This automatic path is different from the manual `InsertMetadata` operation. ```text URL Parameter Set path = capture configured visitor URL parameters and automatically attach resulting Metadata during purchase flow InsertMetadata path = manually add Metadata to a specific existing item ``` Both can create Metadata, but they are not the same workflow. Use URL Parameter Sets when the business wants RevCent to capture visitor URL parameters before purchase. Use `InsertMetadata` when a workflow, external system, AI Assistant, AI Voice Agent, Function, or API client needs to add Metadata to a known item after the item exists or outside the automatic purchase flow. --- ## URL Parameter Set vs Tracking Domain URL Parameters RevCent tracking can involve parameters configured directly on a Tracking Domain or through a reusable URL Parameter Set. | Method | Best Use | |---|---| | URL Parameter Set | Reusable parameter groups that can be attached to one or more Tracking Domains. | | Tracking Domain URL parameters | One-off parameters that apply only to a specific Tracking Domain. | Preferred approach: ```text Use URL Parameter Sets when the same parameter group should be reused, standardized, or maintained consistently. Use direct Tracking Domain URL parameters only when a parameter is truly domain-specific. ``` URL Parameter Sets are easier to maintain because the business can update a reusable set instead of duplicating the same parameter rules across multiple Tracking Domains. --- ## URL Parameter Rows Each URL parameter row tells RevCent what to capture and how long to preserve it. The web app describes each row as containing: ```text URL Parameter Cookie Name Days Default Value ``` The API/MCP schema describes the saved-name behavior as `metadata_name`. Conceptually: | Setting | Purpose | |---|---| | URL Parameter | Query parameter RevCent should look for in the visitor URL. | | Cookie Name / Metadata Name | Name RevCent should use when saving the captured value. | | Days | How long RevCent should preserve the value for the visitor. | | Default Value | Optional fixed value to save instead of the URL's actual value when the parameter is present. | Example row: ```json { "url_parameter": "utm_source", "metadata_name": "utm_source", "days": 30 } ``` If a visitor arrives at: ```text https://example.com/?utm_source=facebook ``` RevCent can preserve: ```text utm_source = facebook ``` --- ## Parameter Naming Strategy Good URL Parameter Sets are intentionally named and consistent. Use parameter names that are clear and stable: ```text utm_source utm_medium utm_campaign utm_content utm_term affiliate_id click_id landing_page checkout_page ``` Avoid inconsistent names for the same concept: ```text source traffic_source utmSource utm_source ``` unless the business has a clear reason to preserve each as a distinct value. Consistency matters because the captured parameter names become durable Metadata names and are later visible on related records. --- ## Default Values Default values are optional and should be used carefully. A default value tells RevCent to save a fixed value when the URL parameter is present. Most setups should leave default value blank so the real visitor URL value is preserved. Use a default value only when the business intentionally wants a fixed value for a known link pattern. Example use: ```text Parameter exists: affiliate_click Default value: affiliate ``` This can mark that the visitor arrived through an affiliate-style link, but it will not preserve the original parameter's unique value unless another parameter captures it. --- ## Days to Save The `days` setting controls how long the captured value should remain associated with the visitor. A common default is 30 days. Examples: | Days | Use Case | |---:|---| | 7 | Short visitor attribution window. | | 30 | Common general-purpose setting. | | 60 | Longer consideration period. | | 90 | Longer funnel or partner cycle. | The correct value depends on how long the business wants visitor parameter context to remain relevant. --- ## Example URL Parameter Set A common ecommerce-style URL Parameter Set might look like this: ```json { "name": "Standard Visitor Attribution Parameters", "description": "Captures UTM, click ID, affiliate, and landing page parameters for tracked visitors.", "enabled": true, "url_parameters": [ { "url_parameter": "utm_source", "metadata_name": "utm_source", "days": 30 }, { "url_parameter": "utm_medium", "metadata_name": "utm_medium", "days": 30 }, { "url_parameter": "utm_campaign", "metadata_name": "utm_campaign", "days": 30 }, { "url_parameter": "utm_content", "metadata_name": "utm_content", "days": 30 }, { "url_parameter": "utm_term", "metadata_name": "utm_term", "days": 30 }, { "url_parameter": "gclid", "metadata_name": "gclid", "days": 30 }, { "url_parameter": "fbclid", "metadata_name": "fbclid", "days": 30 }, { "url_parameter": "affiliate_id", "metadata_name": "affiliate_id", "days": 30 }, { "url_parameter": "sub_id", "metadata_name": "sub_id", "days": 30 }, { "url_parameter": "landing_page", "metadata_name": "landing_page", "days": 30 } ] } ``` The exact list should match the business's real traffic sources, affiliate platforms, ad platforms, and funnel links. --- ## Creating a URL Parameter Set A user can create a URL Parameter Set in the web app by going to the URL Parameter Sets area and creating a new set. Core setup fields include: ```text name description status / enabled state url parameters ``` In API/MCP workflows, use the URL Parameter Set creation operation only after the desired parameters are known. A good setup process is: ```text Identify traffic sources ↓ Identify URL parameters used in links ↓ Choose saved Metadata names ↓ Choose days-to-save values ↓ Create URL Parameter Set ↓ Attach it to Tracking Domain(s) ↓ Test visitor URLs ``` --- ## Editing a URL Parameter Set A user can edit an existing URL Parameter Set from the web app by opening the set and changing the details or parameter rows. Be careful when editing parameter names or saved names. Changing a URL Parameter Set affects future capture behavior. It does not rewrite old visitor or purchase Metadata that was already captured. Before editing, verify: ```text Which Tracking Domains use this set? Which parameters are currently present? Whether the business still uses those link parameters? Whether changing saved names could split future Metadata from historical Metadata? Whether default values are intentionally configured? ``` --- ## API and MCP Operations The MCP overview identifies the core URL Parameter Set operations as: | Operation | Purpose | |---|---| | `GetUrlParameterSets` | List URL Parameter Sets with pagination. | | `GetUrlParameterSet` | Retrieve one URL Parameter Set by ID. | | `CreateUrlParameterSet` | Create a reusable URL Parameter Set. | | `EditUrlParameterSet` | Edit an existing URL Parameter Set. | Related Tracking Domain operations are also important because the set must be attached to a Tracking Domain before it can capture parameters for that domain. Important rule: ```text CreateUrlParameterSet creates the reusable set. EditTrackingDomain attaches the set to the Tracking Domain. ``` --- ## AI and MCP Guidance AI/MCP clients should treat URL Parameter Sets as configuration that affects future visitor capture. Safe workflow for creation: ```text 1. Determine which domains are tracked. 2. Determine which traffic sources and link parameters the business uses. 3. Build a parameter list. 4. Use stable saved Metadata names. 5. Use a sensible days value, commonly 30. 6. Create the URL Parameter Set. 7. Attach it to the intended Tracking Domain(s). 8. Verify the Tracking Domain association. 9. Test a URL containing expected parameters. 10. Confirm the values appear as Metadata on the later visitor/purchase flow. ``` Safe workflow for editing: ```text 1. Retrieve the existing URL Parameter Set. 2. Review the current parameter rows. 3. Confirm which Tracking Domains use the set. 4. Make only intended changes. 5. Avoid renaming saved Metadata names unless the business intentionally wants a new key going forward. 6. Save changes. 7. Test future visitor URLs. ``` --- ## Common Mistakes Avoid these mistakes: - creating a URL Parameter Set but never attaching it to a Tracking Domain - attaching the wrong set to a Tracking Domain - using inconsistent saved Metadata names - using a default value when the real URL value should be preserved - forgetting to save changes after adding URL parameter rows - assuming historical Metadata is rewritten after editing a set - duplicating the same parameter rows separately across many Tracking Domains instead of using a reusable set - forgetting that non-WordPress/custom checkout flows still need to preserve visitor identity into the purchase flow - treating URL Parameter Sets as Metadata records instead of capture configuration --- ## Relationship Summary | Related Concept | Relationship to URL Parameter Sets | |---|---| | Tracking Domain | Uses URL Parameter Sets to know which URL parameters to capture on that domain. | | Metadata | Captured URL parameter values can become Metadata attached to visitors and purchase-related items. | | Tracking Visitor | Preserves visitor identity and captured parameter context before purchase activity occurs. | --- ## Summary URL Parameter Sets are reusable tracking configuration in RevCent. They define which URL query parameters RevCent should capture from visitors on tracked domains. Once attached to a Tracking Domain, a URL Parameter Set helps RevCent preserve visitor source, campaign, affiliate, click, landing page, and other URL-based context. That captured context can become Metadata during the visitor and purchase lifecycle, including automatic attachment during initial purchase flows to records such as the Sale, Customer, Transaction, Shipping, and other related items. Use URL Parameter Sets to standardize visitor parameter capture across one or more Tracking Domains, keep Metadata names consistent, and make conversion attribution easier to maintain over time. --- 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.