Ellipse Gradient for Header

ActionIQ Integration Guide

Connect ActionIQ customer profiles, events, audiences, and activations with enterprise applications through REST APIs, batch exchange, files, and tenant-specific event integrations.

ActionIQ integration options at a glance

ActionIQ integrations are primarily built around tenant-specific REST APIs and ingestion endpoints for customer profiles, events, audiences, and activation data. Batch and asynchronous exchange is also important, using scheduled processing, cloud storage, warehouse-oriented pipelines, or supported data files. Selected ActionIQ features may provide webhook-style or callback notifications, but universal outbound webhooks are not confirmed. Authentication generally uses tenant-issued credentials and permissions, with the precise API-key or token model requiring verification. Martini can consume ActionIQ APIs, submit bounded batches, process files, orchestrate schedules, receive documented callbacks, map data, and coordinate downstream delivery.

Integration pointSupported by ActionIQ?Common use casesHow Martini supports it
REST APIsYesActionIQ REST-style APIs support profile and event ingestion, audience or activation exchange, and integration with external applications. Exact endpoints depend on the tenant and enabled modules.Martini can consume ActionIQ REST APIs from workflows, send transformed requests, expose REST APIs for inbound integration, and centralize response handling.
Bulk / async / batch APIsYesBatch ingestion and scheduled exchange are important for customer profiles, Events, Audiences, and activation data. Job and status behavior is tenant-dependent.Martini can create bounded batches, orchestrate asynchronous submission and status checks, persist batch metadata, and retry transient failures.
Webhooks / outbound callbacksLimitedSelected ActionIQ features may provide event-driven or real-time notifications, but universal outbound webhooks for all objects are not confirmed.Where a documented callback exists, Martini can receive it through a webhook-triggered workflow, validate the notification, retrieve current data, and continue processing.
File exchangeLimitedCustomer, event, and audience data may be exchanged through delimited files, JSON, cloud object storage, or other tenant-supported batch locations.Martini can prepare, validate, transform, retrieve, and deliver files, then coordinate processing status and downstream reconciliation.
Database / analytics accessLimitedActionIQ may participate in warehouse and analytics architectures through Snowflake, Databricks, lakehouses, or other supported data platforms. Direct application-database access is not assumed.Martini can query or write supported external databases and coordinate the resulting data exchange with ActionIQ APIs or files.
AuthenticationLimitedTenant-issued API credentials, authorization headers, and permissions are expected, but the exact API-key, token, header, and scope model varies by endpoint.Martini can store credentials in secure configuration and secrets, apply endpoint-specific authentication, and separate environments without embedding secrets in workflows.
GraphQL APIsNot confirmedNo official ActionIQ GraphQL API was verified, so GraphQL should not be assumed for ActionIQ integrations.Martini supports GraphQL consumption generally, but an ActionIQ GraphQL integration should only be implemented if the tenant explicitly documents one.
SOAP APIsNoNo official ActionIQ SOAP API was verified; REST and batch or file exchange are the preferred assumptions.Martini supports SOAP consumption generally, but SOAP should not be selected for ActionIQ without tenant-specific confirmation.

How ActionIQ exposes data and business events

ActionIQ REST APIs

ActionIQ is primarily integrated through HTTP-based APIs and ingestion endpoints. These APIs may support customer profile and Event ingestion, Audience or Activation exchange, and connections to external applications, with endpoint coverage determined by the tenant and enabled modules.

Martini implementation pattern

Martini implementation pattern: Martini authenticates with tenant-issued credentials, invokes the documented ActionIQ endpoint, validates and transforms the response or request, applies identity and consent rules, and persists request, batch, or job metadata for reconciliation.

Implementation sequence

Authenticate using the tenant-approved credential model
Retrieve or receive the source customer, event, audience, or activation data
Validate identifiers, consent fields, and required attributes
Map the data to the ActionIQ or destination model
Submit the request and capture response metadata
Route permanent validation failures separately from retryable transport errors

ActionIQ batch exchange

Bulk, asynchronous, and scheduled exchange is an important ActionIQ operating pattern for profiles, Events, Audiences, and activation data. The implementation may use APIs, cloud storage, supported files, or warehouse-oriented pipelines.

Martini implementation pattern

Martini implementation pattern: A scheduled workflow selects an incremental source window, creates bounded batches or files, submits them through the confirmed ActionIQ path, polls or receives status where available, and records watermarks and processing outcomes.

Implementation sequence

Start the workflow on a controlled schedule
Read the incremental source window
Validate and partition data into bounded batches or files
Submit the batch through the confirmed ActionIQ interface
Check processing or job status when the tenant provides it
Store the watermark, batch identifier, and reconciliation totals

ActionIQ webhook-style notifications

ActionIQ supports event-driven and real-time movement in selected areas, but a general-purpose outbound webhook facility for every object is not confirmed. Availability must be verified for the specific feature or job.

Martini implementation pattern

Martini implementation pattern: Where ActionIQ exposes a documented callback, Martini receives the notification through a webhook-triggered workflow, authenticates or validates the request, retrieves authoritative data if necessary, and prevents duplicate processing using event or job metadata.

Implementation sequence

Receive the documented ActionIQ callback
Validate the notification and tenant context
Check whether the event or job was already processed
Retrieve the current resource or activation status when required
Map and route the resulting data
Persist the callback and processing outcome

ActionIQ files and warehouse exchange

ActionIQ-related data may be exchanged through supported files, cloud storage, Snowflake, Databricks, or another warehouse or lakehouse. Direct access to the ActionIQ application database is not assumed.

Martini implementation pattern

Martini implementation pattern: Martini reads or writes the confirmed external data interface, validates file or table structure, transforms profiles and Events into the ActionIQ model, and coordinates API submission or downstream delivery with operational checkpoints.

Implementation sequence

Connect to the confirmed file or warehouse location
Read the approved file or incremental data set
Validate schema, identifiers, dates, and consent fields
Transform rows into the required ActionIQ or destination structure
Submit or deliver the transformed data
Record file, partition, watermark, and outcome metadata

Common ActionIQ integration patterns

Pattern 1: Synchronize CRM customers and activity to ActionIQ

When to use this pattern

Use this pattern when Salesforce or another operational CRM is the source of customer attributes, account relationships, leads, opportunities, and activity that should contribute to ActionIQ profiles and behavioral data.

Integration direction
Salesforce
Martini
ActionIQ
Example Mapping
ActionIQ FieldCanonical FieldTarget Field
Salesforce ContactIdsourceCustomerIdCustomer profile identifier
Salesforce EmailemailCustomer profile email
Salesforce LastModifiedDatesourceUpdatedAtProfile update timestamp
Salesforce Activity.TypeeventTypeEvent type
Martini implementation pattern

A scheduled Martini workflow reads changed Salesforce objects, preserves stable source identifiers, validates consent and required attributes, maps profiles and activity into ActionIQ payloads, submits bounded batches, and stores the source watermark. Permanent schema failures are isolated while transient HTTP or throttling failures are retried.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • validation
  • batch orchestration
  • error handling

Pattern 2: Activate ActionIQ audiences in an engagement platform

When to use this pattern

Use this pattern when approved ActionIQ Audiences or Segments must be synchronized to Braze or Iterable for lifecycle messaging, personalization, suppression, or campaign targeting.

Integration direction
ActionIQ
Martini
Braze
Example Mapping
ActionIQ FieldCanonical FieldTarget Field
ActionIQ profile identifiercustomerIdExternal user ID
ActionIQ audience membershipaudienceMembershipSegment membership
ActionIQ consent statusmarketingConsentSubscription state
ActionIQ export timestampaudienceVersionSync metadata
Martini implementation pattern

Martini retrieves or receives the ActionIQ export, verifies audience version and consent, applies add and remove rules, transforms identifiers and attributes to the engagement platform model, and submits controlled batches. The workflow records destination responses and prevents duplicate audience versions from being reprocessed.

Martini capabilities used
  • workflow orchestration
  • REST API consumption
  • data transformation
  • business rules
  • idempotency controls
  • reconciliation

Pattern 3: Load warehouse profiles and Events into ActionIQ

When to use this pattern

Use this pattern when Snowflake, Databricks, or another supported warehouse or file location is the source of truth for incremental customer and behavioral data.

Integration direction
Snowflake
Martini
ActionIQ
Example Mapping
ActionIQ FieldCanonical FieldTarget Field
warehouse.customer_idsourceCustomerIdCustomer profile identifier
warehouse.emailemailCustomer profile email
warehouse.event_nameeventTypeEvent type
warehouse.event_timeeventTimestampEvent timestamp
Martini implementation pattern

A scheduled Martini workflow reads a bounded incremental window, validates schema and identity fields, transforms warehouse rows into ActionIQ profile and Event models, partitions payloads according to confirmed limits, and submits them through the tenant's ingestion path. Watermarks, batch identifiers, rejected rows, and retry outcomes are retained for replay.

Martini capabilities used
  • SQL or file access
  • scheduled workflows
  • mapping and transformation
  • validation
  • batch processing
  • monitoring

Pattern 4: Deliver approved ActionIQ audiences to advertising platforms

When to use this pattern

Use this pattern when consented ActionIQ Audiences must be delivered to Google Ads or Amazon Ads for activation, suppression, or measurement, subject to confirmed tenant and destination support.

Integration direction
ActionIQ
Martini
Google Ads
Example Mapping
ActionIQ FieldCanonical FieldTarget Field
ActionIQ audience IDaudienceIdCustomer list or audience identifier
ActionIQ profile identifiercustomerIdMatched customer identifier
ActionIQ consent statusactivationConsentEligibility rule
ActionIQ export versionexportVersionActivation metadata
Martini implementation pattern

Martini coordinates the approved ActionIQ export, checks consent and regional suppression rules, transforms the audience to the confirmed advertising-platform interface, submits bounded requests, and tracks accepted, rejected, and removed members. Failed batches are replayed using stable export and audience metadata rather than creating a new uncontrolled activation.

Martini capabilities used
  • API orchestration
  • data mapping
  • business rules
  • privacy validation
  • batch processing
  • retry and reconciliation

Applications commonly integrated with ActionIQ

ActionIQ commonly participates in customer-data, warehouse, engagement, and advertising architectures. The exact destination, export, and authentication capabilities should be verified for the ActionIQ tenant and connected application; Martini can orchestrate the confirmed APIs, files, warehouse interfaces, and activation workflows.

Application Scenario Direction Martini Pattern
Salesforce Combine CRM attributes, account relationships, lead activity, and opportunity context with behavioral data in ActionIQ, with selected audiences or insights potentially flowing back to Salesforce. Salesforce → Martini → ActionIQ A scheduled Martini workflow reads changed Salesforce objects, preserves source identifiers, maps attributes to ActionIQ customer profiles, converts relevant activity into Events, submits bounded batches, and records validation and transport outcomes.
Snowflake Use warehouse data as a source for ActionIQ customer profiles, events, segmentation, and analytics, or exchange activation results with the warehouse. Snowflake → Martini → ActionIQ Martini queries incremental Snowflake data or reads an approved exchange location, applies identity and consent rules, transforms rows into the ActionIQ ingestion model, submits batches, and stores watermarks and job status.
Databricks Exchange lakehouse customer and event data with ActionIQ for unified profiles, segmentation, and activation workflows. Databricks → Martini → ActionIQ A Martini workflow retrieves incremental lakehouse data through the supported database or file interface, validates schema and identifiers, maps records to ActionIQ profiles and Events, and routes rejected rows for operational review.
Braze Activate ActionIQ audiences and customer attributes for mobile, email, and in-app engagement. ActionIQ → Martini → Braze Martini retrieves or receives an approved ActionIQ audience export, maps stable profile identifiers and attributes to Braze, applies consent and suppression rules, upserts members in batches, and reconciles accepted and rejected counts.
Iterable Send audience membership and profile attributes to support lifecycle messaging and campaign targeting. ActionIQ → Martini → Iterable A workflow retrieves an ActionIQ audience or activation result, transforms profile and subscription fields to Iterable's API model, handles additions and removals, and retries only transient destination failures.
Google Ads Activate consented ActionIQ audiences for advertising, suppression, and measurement use cases. ActionIQ → Martini → Google Ads Martini validates audience approval and consent status, retrieves the ActionIQ export, transforms identifiers to the confirmed Google Ads interface, submits controlled batches, and tracks audience version and activation status.
Amazon Ads Deliver approved customer audiences for advertising activation and measurement. ActionIQ → Martini → Amazon Ads A Martini workflow coordinates the ActionIQ export, applies regional privacy and suppression rules, submits audience data through the supported Amazon Ads path, and records export, batch, and destination results.
Adobe Experience Cloud Exchange customer, audience, and behavioral data across marketing and analytics products. ActionIQ → Martini → Adobe Experience Cloud Martini orchestrates the confirmed ActionIQ and Adobe APIs or file exchanges, maps profile and audience identifiers, applies destination-specific rules, and provides centralized retry, logging, and reconciliation.

How to build a ActionIQ integration in Martini

Objective

Establish tenant-specific access to ActionIQ and any source or destination applications without embedding credentials in workflow logic.

Instructions in Martini

  • Confirm the ActionIQ endpoint, tenant, credential type, authorization headers, and permissions
  • Store credentials and environment-specific values in secure Martini configuration or secrets
  • Validate access with a non-destructive request
  • Document source and destination identifiers

Objective

Select a trigger that matches the required latency and the ActionIQ capability confirmed for the tenant.

Instructions in Martini

  • Use a scheduler for incremental or batch exchange
  • Use a webhook-triggered workflow only for a documented ActionIQ callback
  • Use an API-triggered workflow when an external application must initiate processing
  • Define overlap and concurrency behavior for scheduled runs

Objective

Read profiles, Events, Audiences, Activations, files, or warehouse rows using the confirmed interface.

Instructions in Martini

  • Use incremental timestamps, sequence values, or change-data-capture where available
  • Retrieve authoritative resource details after a callback when necessary
  • Capture pagination, batch, export, and job identifiers
  • Keep the source watermark outside the individual request payload

Objective

Coordinate calls, file handling, validation, transformation, business rules, and downstream delivery as a maintainable Martini workflow.

Instructions in Martini

  • Separate extraction, validation, transformation, submission, and reconciliation stages
  • Use bounded batches and controlled concurrency
  • Route permanent data failures separately from transient transport failures
  • Make replay and partial failure behavior explicit

Objective

Convert ActionIQ and adjacent-system data into a canonical model while preserving identity, consent, and operational metadata.

Instructions in Martini

  • Map stable source identifiers rather than relying only on mutable email addresses
  • Normalize timestamps, enumerations, nulls, and event types
  • Include audience versions, export timestamps, batch IDs, and source metadata
  • Version mappings when schemas or destination requirements change

Objective

Enforce identity, consent, suppression, audience lifecycle, and data-quality rules before data is submitted or activated.

Instructions in Martini

  • Validate required profile and Event fields
  • Apply regional privacy, consent, and opt-out rules
  • Define add, remove, merge, split, and deletion behavior
  • Prevent duplicate processing with stable event, export, or batch keys

Common ActionIQ data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
Customer profilesUnified customer or household-level profiles assembled from source attributes and behavioral activity.Salesforce, Snowflake, Databricks, Braze, Iterable, Adobe Experience CloudMartini maps stable source identifiers and attributes, validates identity and consent fields, submits profile upserts where supported, and records source-to-ActionIQ mappings.
EventsBehavioral or transactional activity such as purchases, page views, and engagement events associated with a customer profile.ActionIQ ingestion endpoints, Snowflake, Databricks, Braze, IterableMartini normalizes event timestamps and identifiers, applies deterministic event keys where supported, batches submissions, and separates validation errors from retryable transport failures.
AudiencesGroups of profiles selected using attributes, Events, and business rules for targeting, analysis, or activation.Braze, Iterable, Google Ads, Amazon Ads, SalesforceMartini retrieves or receives audience exports, applies consent and suppression rules, maps memberships to destination models, and reconciles selected, exported, accepted, and rejected counts.
SegmentsLogical subsets of customer profiles used for analysis, targeting, or activation.ActionIQ, advertising platforms, engagement platforms, data warehousesMartini treats segment exports according to their snapshot or incremental semantics, attaches version metadata, and coordinates downstream delivery or storage.
JourneysCustomer engagement or orchestration definitions that use audience and event data to coordinate downstream actions.Braze, Iterable, Adobe Experience Cloud, internal servicesMartini can receive documented journey-related notifications or coordinate supporting data flows, while leaving ActionIQ journey execution to the tenant's configured capabilities.
ActivationsExports or deliveries of audience and customer data to downstream destinations.Braze, Iterable, Google Ads, Amazon Ads, SalesforceMartini orchestrates activation retrieval or delivery, transforms destination payloads, tracks export and batch identifiers, and manages retry and reconciliation logic.

Authentication and security considerations

Tenant-specific authentication

ActionIQ authentication is endpoint- and tenant-dependent. API credentials, authorization headers, and tenant permissions are expected, but the exact API-key or token model, header name, lifetime, and scope behavior must be confirmed in the ActionIQ environment.

Secure credential handling

Martini can keep environment-specific credentials in secure configuration and secrets rather than embedding them in workflows. Access should be restricted to the required profiles, Events, Audiences, and activation operations.

Customer-data protection

  • Preserve stable source identifiers while limiting unnecessary personal data in logs.
  • Apply consent, suppression, regional privacy, and opt-out rules before activation.
  • Use separate credentials and permissions for sources, destinations, storage, and warehouse connections where required.

Operational considerations for ActionIQ integrations

Batching and rate limits

Confirm ActionIQ request-size, batch-size, concurrency, and throttling behavior for each tenant endpoint. Use bounded batches, controlled concurrency, and exponential backoff for transient failures such as HTTP 429 responses.

Incremental processing

Use source timestamps, sequence values, or change-data-capture feeds and store the last successful watermark outside the request payload. Prevent overlapping scheduled runs from processing the same source window concurrently.

Idempotency and replay

Use stable event, export, audience, or batch identifiers where supported. Store request IDs, batch IDs, audience versions, and job statuses so failed work can be replayed without duplicating Events or audience changes.

Schema and lifecycle changes

Validate identifiers, dates, enumerations, null handling, and consent fields before submission. Treat full snapshots, incremental add or remove exchanges, and point-in-time activations differently, and version mappings when tenant or destination schemas change.

Monitoring and testing

Monitor authentication failures, schema errors, stale exports, unexpected volume changes, repeated retries, and rejected rows. Test with representative data while avoiding unnecessary personal information in logs.

Why use Martini instead of scripts or point-to-point integrations?

Centralized orchestration

Scripts often combine extraction, transformation, submission, retries, and monitoring in one code path. Martini separates these concerns into workflows and reusable integration assets that can be maintained as ActionIQ tenants and downstream systems change.

Flexible integration methods

Martini can consume ActionIQ REST APIs, expose APIs for surrounding applications, process files, connect to supported warehouses, and receive documented callbacks without requiring a dedicated ActionIQ connector.

Reliable data movement

Workflows can apply validation, consent rules, identity mapping, batching, idempotency, retry handling, and reconciliation consistently across profile, Event, Audience, Segment, Journey, and Activation flows.

Operational visibility

Centralized logs and workflow controls make it easier to trace batch identifiers, watermarks, audience versions, rejected rows, and downstream responses than with isolated point-to-point scripts.

Frequently asked questions

How can ActionIQ be integrated with enterprise systems?

ActionIQ can be integrated primarily through tenant-specific REST APIs and ingestion endpoints, with batch, asynchronous, file, cloud-storage, warehouse, and selected event-driven patterns also available depending on the implementation. Customer profiles, Events, Audiences, Segments, Journeys, and Activations can be exchanged with operational applications, data platforms, engagement tools, and advertising destinations.

Can Martini integrate with ActionIQ?

Yes. Martini can integrate with ActionIQ by consuming its documented REST APIs, submitting profile and Event batches, coordinating file or warehouse exchanges, and receiving webhook-style notifications where the tenant exposes a documented callback. Martini can also map, validate, schedule, and reconcile the resulting data flows.

Do I need a connector to integrate ActionIQ with Martini?

No. A dedicated ActionIQ connector is not required. Martini can use ActionIQ's confirmed native integration mechanisms, including REST APIs, batch or file exchange, tenant-specific authentication, external warehouse interfaces, and documented callbacks.

Is there any extra Lonti cost to integrate ActionIQ with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate ActionIQ. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from ActionIQ, cloud infrastructure, data warehouses, advertising platforms, or other third-party services based on subscription, usage, and deployment model.

Which ActionIQ integration methods should be used?

REST APIs are the primary integration method for profile, Event, Audience, and Activation use cases. Batch and asynchronous exchange are important for larger data volumes, while supported files, cloud storage, and external warehouse interfaces can suit scheduled pipelines. GraphQL and SOAP should not be assumed because no official ActionIQ interfaces were confirmed.

Does ActionIQ provide webhooks or callbacks?

ActionIQ supports real-time and event-oriented movement in selected areas, but universal outbound webhooks for every object were not confirmed. Martini can receive a documented ActionIQ callback through a webhook-triggered workflow when the specific audience, activation, event, or job supports it.

How does synchronization between ActionIQ and other systems work?

Synchronization can use scheduled incremental workflows, API-triggered processing, documented callbacks, batch files, or warehouse exchange. Martini can maintain watermarks, audience versions, export and batch identifiers, identity mappings, consent rules, and reconciliation totals so that additions, changes, removals, and late-arriving data are handled explicitly.

How does Martini handle ActionIQ mapping, errors, and duplicates?

Martini can map and transform ActionIQ profiles, Events, Audiences, and Activations to canonical or destination models, validate required fields, and apply consent and business rules. Workflows can distinguish permanent validation failures from retryable transport or throttling errors, retain batch metadata, and use deterministic event or export keys to support idempotent replay.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Build a maintainable ActionIQ integration

Use Martini to connect ActionIQ with customer applications, data platforms, engagement tools, and activation destinations through secure APIs, workflows, mappings, and operational controls.

EXPLORE MARTINI
BOOK A DEMO