Skip to content
Get Support ⤴
  • There are no suggestions because the search field is empty.

Klaviyo

Connect Anedot to Klaviyo to automatically sync donation and lead data and view supporter activity through Klaviyo Profiles—supporting both financial and non-financial event relays.

Klaviyo is a marketing automation platform built for personalized, behavior-based outreach. It enables organizations to engage supporters through highly targeted email, SMS, and mobile push campaigns.

Table of Contents

Connecting Anedot to Klaviyo

To connect your Anedot account to Klaviyo:

  1. Choose Action Pages to Sync

    • By default, all Action Pages are included.

    • To exclude specific pages, enter a comma-separated list of Action Page IDs.

  2. (Optional) Scope the integration to a specific Team to limit data sync access.

  3. Enter Your Klaviyo API Key

    • Be sure to use a Private API Key.

    • Public API Keys will not work for relays.

  4. Save Your Settings

    • Once saved, your connection is live.

Action Pages, Team access, and credentials can be updated at any time.

Data Relays

  • Anedot sends relays from both Donation Pages and Lead Pages to Klaviyo.

  • Custom fields are not relayed at this time.

  • Push Unsent functionality allows you to resend failed or historical donations by specifying a date range.

    • After 5 consecutive relay failures, the integration is marked inactive and stops attempting to send data.

Viewing Data in Klaviyo

Once a relay is successful:

  • Go to the Profiles tab in Klaviyo.

  • Search for a supporter by name, email, or other identifiers.

  • Each Profile contains a full history of the supporter’s donations and lead submissions synced from Anedot.

Field Mapping​

The Anedot Fields match the Submission’s Raw Data and the Klaviyo Fields match the Request Body relay.

Anedot Field Klaviyo Field
“event” type
-
createdAt
amount (x100)
"Anedot: Submission Created"		 attributes 
{time}
{value}
{metric name }
-
address {postalCode} 
address {city} 
email
address {region} 
address {country} 
lastName
firstName
phone		 profile 
{zip}
{city}
{email}
{region}
{country}
{last_name}
{first_name}
{phone_number}
(Submission) id unique_id
-
utmCodes {term}
** utmCodes {medium}
** utmCodes {source}
** {sourceCode}
utmCodes {content}
** utmCodes {campaign}**
accountName		 properties  
{utm_term}
{utm_medium}
{utm_source}
{source_code}
{utm_content}
{utm_campaign}
{anedot_account}

**UTM Codes can be added to the Page URL .

Payload Data

Request Headers

{ }

Request Body

{
  "type": "event",  
  "attributes": {  
    "time": "2023-05-15T16:37:30.844Z",  
    "value": 200.0,  
    "metric": {
      "name": "Anedot: Submission Created"  
    },  
    "profile": {  
      "zip": "70112",  
      "city": "New Orleans",  
      "email": "[[email protected]](/cdn-cgi/l/email-protection)",  
      "region": "LA",  
      "country": "US",  
      "last_name": "Dot",  
      "first_name": "Annie",  
      "phone_number": "1231231234"  
    },  
    "unique_id": "e1c0b789-81c5-489c-959f-e30ca6fa4c9a",  
    "properties": {  
      "utm_term": null,  
      "utm_medium": null,  
      "utm_source": null,  
      "Source Code": null,  
      "utm_content": null,  
      "utm_campaign": null,  
      "Anedot Account": "The Charitable Foundation"  
    }
  }  
}

Response Body (Success)

{ } 

Response Body (Failure)

{ 
  "errors": [{ 
    "id": "df5497da-4e89-4f5a-a019-3f5d1d772015",  
    "code": "not_authenticated",  
    "title": "Authentication credentials were not provided.",  
    "detail": "Missing or invalid private key.",  
    "source": { 
      "pointer": "/data/"  
    },  
    "status": 401  
  }]  
}

Response Status (Success)

202

Response Status (Failure)

401