InMarket

Send conversion and engagement events to InMarket server-to-server for location-based attribution, audience intelligence, and real-time campaign measurement.

⚠️

This blueprint is currently alpha — schema and behaviour may change before GA.

Prerequisites

Complete these steps before configuring Signal. InMarket is an enterprise platform that requires direct engagement with their sales team.

Contact InMarket sales

InMarket does not offer self-service sign-up. Contact the InMarket sales team at inmarket.com to set up an account and discuss your attribution requirements.

Receive your credentials from your account manager

After onboarding, your InMarket account manager will provide:

API Key — authenticates server-to-server event delivery
Partner ID — identifies your organisation within the InMarket platform

Keep these credentials secure; they cannot be regenerated through a self-service portal.

Obtain your Campaign ID

Your account manager will create campaigns within the InMarket platform. Each campaign has a Campaign ID that you will use to route events to the correct campaign for attribution. Request this from your account manager for each campaign you want to track.

Confirm event schema

Work with your InMarket account manager to agree on the event schema — which events to send, required fields, and expected formats. InMarket may have specific requirements depending on your campaign type (e.g. in-store visits, online purchases).

Configuration

Field	Type	Required	Description
`api_key`	secret	Yes	Your InMarket API key, provided by your account manager.
`partner_id`	string	Yes	Your InMarket partner ID, provided during onboarding.
`campaign_id`	string	Yes	The InMarket campaign ID to associate events with.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find InMarket or filter by Attribution.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/inmarket/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "InMarket",
    "variant": "default",
    "config": {
      "api_key": "your_api_key",
      "partner_id": "partner-xyz-789",
      "campaign_id": "camp-12345"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The Retail variant maps the following Datafly events to InMarket events:

Datafly Event	InMarket Event	Notes
`Product Added`	`add_to_cart`	Cart-stage event
`Order Completed`	`purchase`	Requires `orderId`, `amount`, `currency`, plus location data when available
Custom events	Passed through	Schema agreed with your account manager

Identity

The default blueprint forwards the following identifiers to InMarket:

Source	InMarket field
`user_id`	`customer_id`
`context.ip`	`ip_address`
`context.user_agent`	`user_agent`

InMarket’s strength is location attribution — include geolocation data (latitude, longitude) and store identifiers in event properties when available.

Default consent category: advertising.

InMarket specialises in location-based attribution. Including geolocation data (latitude, longitude) and store identifiers in your events significantly improves attribution accuracy.

Verify it’s working

Coordinate with your InMarket account manager to confirm test mode or sandbox availability.
In the Signal Management UI, open your InMarket integration and watch the Live Events stream as you trigger events.
Ask your account manager to verify the event was received on their end.
Confirm 200 responses in Signal’s Live Events log.
Review campaign reports in InMarket once test events are confirmed.

Troubleshooting

Symptom	Cause	Resolution
`401 Unauthorized`	Invalid API key	Contact your InMarket account manager to verify or regenerate the API key.
`400 Bad Request`	Missing required fields	Verify the event payload matches the agreed schema with InMarket.
Events not appearing	Wrong campaign ID	Confirm `campaign_id` with your account manager.
Attribution gaps	Missing location data	Include geolocation data in events where available for better attribution.

Visit InMarket or contact your account manager for full API documentation and support.

Blueprint

The InMarket blueprint version is 0.1.0 (alpha). It ships with a Retail variant covering add_to_cart and purchase events. Location data is supplied through event properties when available.