Entity sync

Entity sync sends your entities to Klaviyo as custom objects, each one linked to its customer’s profile. A dog food brand can segment on breed or age, or send a birthday email from each dog’s date of birth, without copying anything by hand.

What you get

• One Klaviyo record per entity, with its name and every attribute, linked to the customer by email.
• Changes as they happen. Creating or editing an entity in Gro, the portal or the API updates its Klaviyo record.
• Clean removal. Archiving or deleting an entity in Gro deletes its Klaviyo record. An archived entity stays in Gro with its history.

Before you start

• Klaviyo connected. If you connected before entity sync existed, click Reconnect on the Klaviyo settings page so Gro can use custom objects.
• At least one entity, so its type shows up in the list.

Turn it on

1. Go to Settings > Integrations, open the menu next to Klaviyo and click Settings.
2. Next to each entity type you want in Klaviyo, click Map and pick an object:
   • Create a new object in Klaviyo. Gro builds the object with a field for every attribute that type has today, and links it to profiles. It belongs to the Gro app in Klaviyo.
   • An existing object. Use one you already set up in Klaviyo.
3. Switch on Sync entities to Klaviyo. Gro sends every entity of each mapped type straight away, then keeps them up to date.

Using an object you built in Klaviyo

Gro sends each entity in this shape:

{
  "object_record": {
    "id": "<entity id>",
    "entityid": "<entity id>",
    "name": "Max",
    "entity_type": "dog",
    "profile_id": "<Gro profile id>",
    "is_active": true,
    "created_at": "2026-10-01T09:30:00.000Z",
    "updated_at": "2026-10-20T14:02:00.000Z",
    "breed": "Collie",
    "age": 4
  },
  "relationships": {
    "email": [{ "id": "<entity id>", "email": "customer@example.com" }]
  }
}

Every attribute sits next to the fixed fields in object_record. When you map the object’s fields in Klaviyo:

• Its ID has to come from object_record.id (or object_record.entityid). Gro removes records by entity ID, so it refuses any other ID.
• Link it to profiles by email from relationships.email.
• Number fields set as whole numbers in Klaviyo get rounded before Gro sends them.

Good to know

• Fields on a Klaviyo object are fixed once it is live. If you add a new attribute later, add the field in Klaviyo yourself, or map the type to a new object.
• Stop syncing on a type leaves its records in Klaviyo. Archive the entities first if you want them gone.
• Turning sync off stops new updates. Nothing already in Klaviyo is removed.