---
# System prepended metadata

title: "\U0001F4AB Segment Partner Destination Documentation Template"

---

# 💫 Segment Partner Destination Documentation Template

> Hi Partners 👋🏼
> 
> Welcome to Segment - glad to have you onboard! This doc serves as a guideline for your team to create best-in-class documentation alongside your amazing product.
> 
> At Segment, we believe that documentation is crucial in delivering the best experience for our mutual customers so we want to think with the following mindset:
>
>+ Be succinct and simple in your writing. Reduce text bloat where possible.
>+ Avoid 1st person language as it’s confusing for customers if they don’t know who wrote the docs (Segment or the Partner).
>+ Where pre-reading is required, hyperlink to other more generic parts of Segment’s (or your) documentation.
>
>+ Provide actionable code samples for each API method.
>
>+ If you would like to include screenshots, please send the original image to us via partner-support@segment.com with naming corresponding to where you've included it within the Markdown below. We prefer PNG images within 400px - 1200px. If you'd like to submit a GIF, please keep under 15MB. Generally you should be able to write these out as text, so only use them when there's something really hard to explain.
>
> The below template intends to provide a standardized structure. Please **make a copy** of this template for editing and submit to the Segment team as a new note on [HackMD.io](https://hackmd.io/). You can view a sample doc as reference here: https://segment.com/docs/destinations/clearbrain/.
> 
> If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!
> 
> If you have any questions in the meantime, please reach out to our team at partner-support@segment.com.


---

## Template begins here...

[Criteo Offline Conversions](https://www.criteo.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) enables offline event tracking so marketers can run Omnichannel Campaigns by leveraging deterministic matching of SKU-level offline sales data with online user profiles.  Criteo can predict which store the shopper prefers to visit and deliver personalized recommendations for products that entice them to visit and purchase.

The Criteo Offline Conversions Destination and this document are maintained by Criteo. For any issues with the destination, please [let us know!](mailto:support@criteo.com).

_**NOTE:** The Criteo Offline Conversions Destination is currently in beta, which means that we are still actively developing the destination. This doc was last updated on October 8, 2019. If you are interested in joining our beta program or have any feedback to help improve the Criteo Offline Conversions Destination and its documentation, please [let  us know](mailto:support@criteo.com)!_


## Getting Started

{{>connection-modes}} 

1. From your Segment UI's Destinations page click on "Add Destination".
2. Search for "Criteo Offline Conversions" within the Destinations Catalog and confirm the Source you'd like to connect to.
3. Input "NA" into "API Key" as this information is not required.
4. Drop your client identifier into "Client ID" into your Segment Settings UI.  You can obtain this ID from your Criteo Account Strategist.

## Track

If you haven't had a chance to review our spec, please take a look to understand what the [Track method](https://segment.com/docs/spec/track/) does. An example call would look like:

```
analytics.track('Order Completed')
```

Track calls will be sent to the Criteo Offline Conversions as a `track` event. The Criteo Offline Conversions Destination is capable of ingesting Track events for offlines sales originating from any source that conforms to [Segment's V2 Ecommerce Events](https://segment.com/docs/spec/ecommerce/v2/). Offline sales originating from a CRM or other source that map to the Order Completed event may be sent to Criteo using the Criteo Offline Conversions Destination. Each 'track' event for an Order Completed must include the products purchased in the offline transaction. A transaction ID, contained in the event.order.id attribute is also required. In addition, a shopper ID, usually a hashed email address, is needed to identify the individual making the purchse. Each product should contain a product ID, price and quantity. The absence of any of this information will trigger an error, casuing the offline sale to be rejected. Please note that offline sales events sent to Criteo are not visible in Criteo's dashboard. These events are used to optimize your campaign and are not made available for analytics or reporting purposes. 

---