Skip to content

Commit a06746b

Browse files
authored
Add Vendo partner page (#1781)
* Create vendo.mdx * Update _meta.ts * Update ad-spend.mdx * Update stripe.mdx * Update ad-spend.mdx * Add files via upload * Update vendo.mdx * Update _meta.ts
1 parent 2ea886d commit a06746b

File tree

12 files changed

+71
-3
lines changed

12 files changed

+71
-3
lines changed

pages/docs/tracking-methods/integrations/_meta.ts

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,5 +24,7 @@ export default {
2424
"newWindow": true
2525
},
2626
"snowplow": "Snowplow",
27-
"stripe": "Stripe"
27+
"stripe": "Stripe",
28+
"tealium": "Tealium",
29+
"vendo": "Vendo"
2830
}

pages/docs/tracking-methods/integrations/ad-spend.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
1+
import { Callout } from 'nextra/components'
2+
13
# Ad Spend
24

3-
Mixpanel’s event-based-data model enables you to represent and analyze any type of data, including ad campaign performance. This guide shows you how to track this data to Mixpanel. The end result is a report that looks like this.
5+
Mixpanel’s event-based data model enables you to represent and analyze any type of data, including ad campaign performance. This guide shows you how to track this data to Mixpanel. The end result is a report that looks like this.
46

57
In this doc, we give step-by-step guidance on how to bring your advertising network data into Mixpanel to look at metrics such as ROAS (Return on Ad Spend), CPC (Cost per click) in the context of in-product conversions. We also provide detailed guides for Google and Facebook Ads. The end result should look like this:
68

@@ -9,6 +11,10 @@ In this doc, we give step-by-step guidance on how to bring your advertising netw
911

1012
**NOTE:** If you are a Marketer reading this, we encourage you to share this with your dev team to get this one-time setup done. This should not take more than a couple of hours.
1113

14+
<Callout type="info">
15+
If you prefer not to build and maintain your data pipelines, consider using [Vendo](/docs/tracking-methods/integrations/vendo). The Vendo integration with Mixpanel allows seamless integration of advertising data from Google, Meta, and other ad platforms into Mixpanel without the need for custom development. Learn more [here](https://www.vendodata.com/connections).
16+
</Callout>
17+
1218

1319
## Understanding the Data Model
1420

pages/docs/tracking-methods/integrations/stripe.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,15 @@
1-
import { Tabs } from 'nextra/components'
1+
import { Tabs, Callout } from 'nextra/components'
22

33
# Stripe
44

55
This guide demonstrates how to stream events from Stripe Webhooks to Mixpanel, via a Google Cloud Function. It requires access to a cloud account and ~10 minutes of setup time.
66

77
Note: This guide assumes you are running in Google Cloud Platform, and have the necessary IAM Access to have Cloud Functions read from GCS. An equivalent process works using AWS Lambda.
88

9+
<Callout type="info">
10+
If you prefer not to build and maintain your data pipelines, consider using [Vendo](/docs/tracking-methods/integrations/vendo). The Vendo integration with Mixpanel enables you to integrate Stripe purchase and subscription data into Mixpanel without needing any custom development. Learn more [here](https://www.vendodata.com/connections/stripe).
11+
</Callout>
12+
913
## Step 1: Create a Cloud Function
1014

1115
Create a [new Cloud Function](https://console.cloud.google.com/functions/add), set the trigger to `HTTPS`, and check the box to Allow Unauthenticated Invocations, since this will be called from Stripe. Copy the URL, which should look something like `https://<zone>-<your-gcp-project>.cloudfunctions.net/stripe-demo`.
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
# Vendo
2+
3+
## Overview
4+
5+
The Vendo integration with Mixpanel enables you to seamlessly sync events and properties across different data sources. This guide provides instructions on how to set up and configure Vendo to sync data to Mixpanel.
6+
7+
## How the Integration Works
8+
9+
Vendo collects event data from various sources like ad platforms, payment platforms and transforms the messages to match Mixpanel’s event schema, and forwards the enriched data into your Mixpanel project. Vendo also archives a copy of the data and can route it to additional storage systems if needed.
10+
11+
Mixpanel is one of the supported downstream destinations for Vendo. With this integration, you can seamlessly send data from your Vendo sources into your Mixpanel project.
12+
13+
For details about connections and configuration options, see [Vendo Developer Docs](https://docs.vendodata.com/en/).
14+
15+
## Prerequisites
16+
17+
Before you begin, ensure you have the following:
18+
- **Vendo Account:** Access to your Vendo dashboard.
19+
- **Mixpanel Project:** An active Mixpanel project with API keys.
20+
- **App Access:** Access to the apps that you want to connect with Vendo.
21+
22+
## Integration Setup
23+
24+
Follow these steps to configure Vendo for sending Google Ads to Mixpanel. The integration flow is similar for all sources.
25+
26+
1. Under Data Import, create a new connection.
27+
28+
![vendo1](/vendo1.png)
29+
30+
2. Select the data source you’d like to integrate to Mixpanel.
31+
32+
![vendo1](/vendo2.png)
33+
34+
3. Click "Connect App".
35+
36+
![vendo1](/vendo3.png)
37+
38+
4. Complete the authentication for the data source.
39+
40+
![vendo1](/vendo4.png)
41+
42+
5. Configure the source.
43+
44+
![vendo1](/vendo5.png)
45+
46+
6. Set Mixpanel as the downstream destination.
47+
48+
![vendo1](/vendo6.png)
49+
50+
7. Provide the details for your target Mixpanel project. These can be found in your project settings.
51+
52+
![vendo1](/vendo7.png)
53+
54+
8. Finalize the connection settings. Provide a name for the integration and optionally provide the start date if you are importing historical data.
55+
56+
![vendo1](/vendo8.png)

public/vendo1.png

202 KB
Loading

public/vendo2.png

360 KB
Loading

public/vendo3.png

330 KB
Loading

public/vendo4.png

288 KB
Loading

public/vendo5.png

236 KB
Loading

public/vendo6.png

206 KB
Loading

0 commit comments

Comments
 (0)