> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/analytics/how-to-configure-limio-for-tracking-and-attribution-in-salesforce-and-zuora.md).
# Configure Tracking in Salesforce and Zuora
Limio provides a generic analytics tracking solution that can be integrated with your analytics or tracking provider. This solution is particularly useful for campaign or partner attribution - especially when you need to report on accurate order numbers from specific campaigns to internal teams or for referral or co-marketing initiatives with partners.
Limio ensures that URL parameters such as UTM and custom tracking parameters persist all the way to the Limio Order. Reporting is available on [Limio Analytics](https://docs.limio.com/product/analytics/limio-commerce-analytics/limio-analytics-new-and-renew-orders), however since full reporting usually takes place in external systems like Zuora or Salesforce, Limio includes native integration with Zuora and supports attribution in Salesforce via Zuora Z360. Limio also offers real-time webhooks, enabling you to push Limio Order data to your analytics systems for accurate attribution.
A separate analytics approach is available for collecting user events via a data layer object. This can be consumed by a tag management system (e.g., Google Tag Manager) and forwarded to tools like Google Analytics or Snowplow. Learn more here: [Configure Limio Data Layer](/product/analytics/how-to-configure-the-limio-data-layer-to-collect-user-events-for-analytics.md).
### Standard parameters, LTM custom parameters, LMO parameter and others
You can configure three types of parameters:
* **Standard parameters**, including [UTM tags](https://en.wikipedia.org/wiki/UTM_parameters) and platform-specific tags from Meta, Google, Reddit, TikTok, and X (Twitter). These are configurable via the referrer. Supported tags include:
* "utm", "ltm", "lmo", "fbclid", "dclid", "gclid", "rdt\_cid", "ttclid", "twclid"
* **Custom parameters (LTM)**, usable in two ways:
* 1\. Configured on a Limio Offer. When a user clicks a Limio Offer via a component (e.g., Offer Cards), LTM parameters (any attribute starting with `ltm_`) will be appended to the URL. These values are offer-specific.
* 2\. Appended directly by the referrer, e.g., `?ltm_partner=BA`.
* These parameters propagate through the registration/log-in, checkout, and order-complete pages.
* **LMO parameter**: This is not customisable. The `lmo_offer` parameter always includes the offer path, e.g., `lmo_offer=/offer2/test-offer`.
Once an order is submitted, Limio stores all tracking parameters in the **tracking** object, which appears in Limio Basket, Limio Orders, Limio Events, and Limio Subscription. Example:
```json
{
"tracking": {
"offers": [
"/offers2/premium"
],
"ltm_OfferDescription": "Premium Monthly Plan - Flash Deal",
"utm_source": "web",
"ltm_CampaignName": "Flash+Sale+$1+first+month,+then+$12.99+per+month",
"ltm_CampaignCode": "PLG_PREM_JUL25",
"addOns": [],
"ltm_ProductType": "SaaS",
"ltm_AccessType": "Direct",
"ltm_analytics_offer_type": "PLGSAAS",
"ltm_CampaignDescription": "$1+for+first+month,+then+$12.99+monthly,+cancel+any+time",
"lmo_offer": "/offers2/PremiumFirstMonth_1USD_Then_1299USD_Monthly",
"referrer": "https://www.example-saas.com/features/project-tracking",
"ltm_TransactionSource": "Web",
"campaign": "/pages2/flash-sale-premium-plan",
"ltm_Target": "5000",
"tag": "/tags/flashsale-premium",
"ltm_CampaignType": "Acquisition"
}
}
```
You can easily access reporting for UTM parameters via Limio Analytics. However, to set up full reporting, the tracking data above can be forwarded to the following systems:
| Destination | How? | Details |
| ----------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Zuora | Via Limio's native integration using custom parameters | Map parameters to Zuora custom fields. [How to populate custom fields in Zuora.](https://docs.limio.com/integrations/zuora-integration/how-to-populate-custom-fields-in-zuora) |
| Salesforce | Via Zuora Z360 | You will first need to set up the Zuora integration above. Requires setup of custom object mapping in Salesforce. Zuora Z360 documentation.
|
| Salesforce | Via Limio-generated Salesforce Platform | Requires Salesforce Lightning Flows. [Activate feature](https://docs.limio.com/integrations/populating-salesforce-data/limio-updates-salesforce) and [set up integration](https://docs.limio.com/integrations/populating-salesforce-data). |
| Any system | Via Limio real-time webhooks | Use the [Order webhook](https://docs.limio.com/developers/webhooks/overview) to send tracking data externally in real-time. |
| Any system | Via Limio APIs | Use the [Get Object -> Order API](https://docs.limio.com/api/objects-api/objects) to pull tracking data externally. You can also do this in batch with the Get Objects operation on the same API. Both are served from your Limio tenant domain (`https://{tenant}/api`). |
To configure custom attributes on Limio Offers that can carry LTM parameters, refer to this guide: [How to work with Templates and Custom Attributes](/product/settings/config-settings/templates-and-custom-attributes.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.limio.com/product/analytics/how-to-configure-limio-for-tracking-and-attribution-in-salesforce-and-zuora.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.