Skip to content

Latest commit

 

History

History
108 lines (71 loc) · 3.71 KB

DESTINATION_TEMPLATE.mdx

File metadata and controls

108 lines (71 loc) · 3.71 KB
Raw
Error in user YAML: (<unknown>): did not find expected key while parsing a block mapping at line 1 column 1
---
title: "Destination_Name"
description: Step-by-step guide on sending your event data from RudderStack to **Destination_Name**.
aliases: ["dest_name","dest_name_2"]  // These alias values are used to optimize the page our search index, making it easier for users to find the integration in the docs.
---

To contributor: Some helpful tips before you get started:

  • Make sure you go through our guide on submitting an integration PR for a quick overview on the things to keep in mind while writing the doc.
  • You can this use this destination doc as a reference for writing your instructions.
  • Do not include any screenshots/images. We will include them after merging the changes.
  • Include tips and suggestions wherever possible.

Destination- Add some introduction about the destination platform.

Find the open source transformer code for this destination in the GitHub repository.

Getting started

RudderStack supports sending events to <Destination_Name> via the following connection modes:

Connection Mode Web Mobile Server
Device mode
Cloud mode

Once you have confirmed that the source platform supports sending events to <Destination_Name>, follow these steps:

  1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select <Destination_Name>.
  2. Assign a name to your destination and click Continue.

Connection settings

To successfully set up Mixpanel as a destination, you need to configure the following settings:

  • <Destination_details>: Enter your <Destination_details> here. <Reference to destination doc/FAQ, if useful/applicable>

Identify

`identify` call A sample `identify` call is shown below: 


Property mappings


The following table lists the mappings between the RudderStack and <Destination_Name> properties:






RudderStack property
<Dest_name> property






(required)



















Track

`track` call

A sample `track` call is shown below:



Page

`page` call

A sample `page` call is shown below:



Group

`group` call

A sample `group` call is shown below:



Screen

`screen` call

A sample `screen` call is shown below:



Common mappings (If any)


The following table lists the common property mappings between the RudderStack and <Destination_Name>:






RudderStack property
<Dest_name> property






(required)



















FAQ