Skip to main content
All CollectionsSources
Firing events and identity enrichments with Zapier
Firing events and identity enrichments with Zapier
Updated over 6 months ago

A "Webhook" action in Zapier can be setup which will carry out two actions in Seeka:

  • Add or update the identity in your Seeka identity graph

  • Fire off the a event to all configured data destinations in Seeka
    โ€‹

OrgId and Converge Key Parameters

  1. The OrgId and Converge key parameters are available in Seeka at https://seeka.app/settings/integrations/api.

  2. Ensure the correct brand is selected in the top right corner - this should be the brand that you wish to forward the event to in the https://seeka.app/settings/integrations/destinations area.

  3. For a full list of supported event types and identity traits head to the identity docs or the event tracking docs.

Tracking an event from Zapier to Seeka

Below settings should be set on your Zapier Webhook action.

Options

  • Zapier action type

    • Webhooks

  • Event

    • Custom request

Headers

  • X-OrgId

    • Set to your Organisation ID

  • X-Converge-Key

    • Set to your Converge Key

  • Content-Type

    • application/json

Request options

Request body

The below covers an example of firing off a Purchase event. Other events can be fired, see event tracking docs for more events.

In the example below, the"activityId" property should be set to the order number or order ID to allow deduplication on Seeka and data destinations.

{
"data": [{
"ev": {
"id": {
"firstName": ["John"],
"lastName": ["Smith"],
"email": ["johnny@smith.com"],
"phone": ["+61422333444"],
"facebook": {
"fbp": ["fb.1.1688633188535.7344101280"],
"fbc": ["fb.1.JHr5DdgFdsFghdGrrDQPf"],
"lead": ["4541354236544"]
},
"ip": ["119.123.34.43"],
"address": [{
"addressLine1": "12 Smith Street",
"countryCode": "AU",
"country": "Australia",
"locality": "Smithville",
"state": "Victoria",
"postcode": "441654"
}]
},
"src": {
"method": "zapier/action",
"origin": "server",
"runtime": {
"type": "zapier"
}
},
"utm": [],
"payload": {
"activityName": "order",
"activityId": "aaa06589-5501-49ff-bc9e-03065d49ee96",
"commerce": {
"products": [{
"currencyCode": "USD",
"productIdentifier": "119933",
"variantIdentifier": "1245663433",
"sku": "sku_product_4",
"lineItemIdentifier": "cc8bac2979ea4f5c9a2e8f25fa7ea6d1",
"productName": "Super awesome product",
"variantName": "Super variant - size medium",
"categoryName": "T shirts",
"brandName": "Tshirts r us",
"unitPrice": 84.33,
"quantity": 1,
"totalDiscount": 0
}, {
"currencyCode": "USD",
"productIdentifier": "442121",
"variantIdentifier": "166544353",
"sku": "sku_product_12",
"lineItemIdentifier": "8c2d8599bf3c4d7ea6ffba40ea8c8784",
"productName": "Very cool product",
"variantName": "Cool variant - size large",
"categoryName": "Bracelets",
"brandName": "Bracelets r us",
"unitPrice": 5,
"quantity": 2,
"totalDiscount": 0
}],
"orderIdentifier": "3075b174947347388e5c13a7df87c341",
"orderNumber": "445778431",
"customerIdentifier": "55381",
"currencyCode": "USD"
}
}
}
}]
}

Sending an identity from Zapier to Seeka

Below settings should be set on your Zapier Webhook action.

Options

  • Zapier action type

    • Webhooks

  • Event

    • Custom request

Headers

  • X-OrgId

    • Set to your Organisation ID

  • X-Converge-Key

    • Set to your Converge Key

  • Content-Type

    • application/json

Request options

Request body

The below covers an example with some identity properties. Other properties can be included, see identity docs for all available properties of an identity.

{
"id": {
"ip": [
"172.217.22.14"
],
"email": [
"jane.doe@gmail.com"
],
"phone": [
"+61422333444"
],
"firstName": [
"Jane"
],
"lastName": [
"Doe"
],
"address": [
{
"countryCode": "AU"
}
],
"dob": [
"2024-05-14T06:05:50.168Z"
],
"facebook": {
"fbc": [
"fb.1.1554763741205.AbCdEfGhIjKlMnOpQrStUvWxYz1234567890"
],
"lead": [
"1554763741205"
]
}
},
"src": {
"method": "zapier/action",
"origin": "server",
"runtime": {
"type": "zapier"
}
}
}
Did this answer your question?