Event Specs

Datafly Signal uses a consistent set of snake_case event IDs across all verticals. These IDs are:

• The value sent in the event field by Datafly.js (e.g. datafly.track('add_to_cart', {...}))
• The key used in your pipeline’s Per-Event Parameters configuration
• The stable identifier used for vendor event name mapping

How event IDs work

Every event flowing through Signal has an event field:

{
  "type": "track",
  "event": "add_to_cart",
  "properties": {
    "currency": "GBP",
    "value": 79.99,
    "items": [
      { "item_id": "SKU-001", "item_name": "Running Shoes", "price": 79.99, "quantity": 1 }
    ]
  }
}

The pipeline engine looks up the event value against your Per-Event Parameters configuration. If a matching section exists, those field mappings are applied on top of the global parameters before delivery to the vendor.

Built-in events

These events are sent automatically by Datafly.js without any track() call:

Common events

These optional events apply across any vertical. They’re documented here so they map consistently across destinations.

Vertical specs

Choose the spec that matches your business model. You can mix events from multiple verticals — a subscription news site might use both Publishing and SaaS events.

Property conventions

All event properties use snake_case:

// Correct
datafly.track('purchase', {
  transaction_id: 'ORD-1234',
  value: 129.99,
  currency: 'GBP',
  items: [{ item_id: 'SKU-001', item_name: 'Trainers', price: 79.99, quantity: 1 }],
});
 
// Avoid
datafly.track('purchase', {
  transactionId: 'ORD-1234',   // camelCase — avoid
  Value: 129.99,               // PascalCase — avoid
});

Standard monetary properties: