Ellipse Gradient for Header

Contentsquare Integration Guide

Connect Contentsquare analytics APIs and exports to enterprise data, reporting, CRM, and operational systems through Martini workflows.

Contentsquare integration options at a glance

Contentsquare provides documented REST APIs for accessing analytics and related project data, with exact endpoints varying by product and API version. Analytics use cases may involve large, asynchronous, batch, or downloadable exports covering projects, segments, metrics, dimensions, and reporting periods. API credentials authorize requests, with access governed by project and account permissions. General-purpose webhooks, public GraphQL APIs, SOAP APIs, and direct database access are not confirmed. Martini can schedule API calls, poll export operations, process JSON or documented export files, transform results, and deliver governed data to databases, warehouses, reporting platforms, CRM systems, or operational APIs.

Integration pointSupported by Contentsquare?Common use casesHow Martini supports it
REST APIsYesAccess Contentsquare analytics and related project data through product-specific documented endpoints.Martini can consume the HTTPS APIs, apply credential-based authentication, transform responses, and expose normalized results through its own APIs.
AuthenticationYesAuthorize API requests with credentials associated with a Contentsquare account, project, site, or workspace.Martini stores credentials in protected Secrets Management and supplies them through environment-specific workflow configuration.
Bulk / async / batch APIsLimitedRequest larger analytics datasets or exports across projects, time ranges, segments, metrics, and dimensions; operations may be asynchronous.Martini can submit an export request, persist a job or report identifier, poll with bounded retries, retrieve the result, and continue processing.
File / attachment APIsLimitedConsume documented downloadable analytics results or export files when the selected Contentsquare API provides them.Martini can process documented JSON, CSV, or other export formats and route them to databases, warehouses, files, or downstream APIs.
Webhooks / outbound callbacksLimitedProduct-specific notifications or integrations may exist, but general-purpose webhook coverage for all analytics events is not confirmed.Martini can receive documented callbacks if a specific Contentsquare product supports them; otherwise scheduled polling is the safer implementation.
Incremental synchronizationLimitedSynchronize reporting windows or newly available exports using timestamps, watermarks, and repeatable query definitions.Martini can persist checkpoints, generate deterministic keys, use half-open time windows, and upsert results into target systems.
Database / analytics accessLimitedObtain analytics data through Contentsquare APIs and exports rather than direct customer database connectivity.Martini can map API or export results into supported SQL databases and data warehouses; direct Contentsquare database access is not assumed.
GraphQL APIsNot confirmedA generally available public Contentsquare GraphQL API was not confirmed.Martini should use the documented Contentsquare REST APIs unless GraphQL support is verified for a specific product or tenant.
SOAP APIsNoNo current public Contentsquare SOAP API was confirmed.Martini should not use SOAP as the default Contentsquare integration approach.

How Contentsquare exposes data and business events

Contentsquare REST APIs

Contentsquare provides documented REST APIs for analytics and related project data. The available endpoint set, request model, and returned objects depend on the selected Contentsquare product and API version.

Martini implementation pattern

Martini implementation pattern: a workflow reads protected credentials and project configuration, calls the appropriate Contentsquare endpoint, validates the response, transforms the analytics model, and sends the result to a target system or internal API.

Implementation sequence

Load the project and reporting configuration
Authenticate the Contentsquare REST request
Retrieve the selected metrics, dimensions, segments, or export
Validate the response and required fields
Map the result to the canonical analytics model
Write the transformed data to the target system

Contentsquare exports and batch processing

Analytics extraction may involve larger time ranges, batch requests, asynchronous export operations, or downloadable datasets. Exact job behavior depends on the selected Contentsquare API product.

Martini implementation pattern

Martini implementation pattern: the workflow submits or initiates the export, stores the returned job or report identifier, polls with a bounded delay and retry policy, retrieves the completed result, and performs an idempotent load.

Implementation sequence

Create the export request for the project and time window
Store the export or report identifier
Poll for completion with bounded retries
Handle failed, expired, or canceled exports
Download or retrieve the completed result
Load the result using a deterministic idempotency key

Contentsquare scheduled synchronization

General-purpose webhook coverage for Contentsquare analytics events is not confirmed, so scheduled retrieval is the safer default for new integrations.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow for a defined reporting window, retrieves new or recently available analytics data, applies a stored watermark, and records the successful checkpoint only after downstream processing completes.

Implementation sequence

Start the workflow on a defined schedule
Calculate the reporting window from the stored watermark
Retrieve the required Contentsquare data
Transform and validate the response
Upsert the result into the destination
Store the last successful watermark

Contentsquare callbacks or notifications

Contentsquare may provide product-specific notifications or integrations in selected areas, but general webhook coverage should not be assumed without product-level verification.

Martini implementation pattern

Martini implementation pattern: where a specific Contentsquare product documents a callback, Martini can receive the notification, retrieve the authoritative resource or export, and process it using the same validation and idempotency controls as a scheduled flow.

Implementation sequence

Verify callback support for the selected Contentsquare product
Receive the documented notification
Retrieve the authoritative analytics result
Validate the event and source identifiers
Transform and deliver the result
Record processing status and prevent duplicates

Common Contentsquare integration patterns

Pattern 1: Load Contentsquare analytics into a warehouse

When to use this pattern

Use this pattern when experience analytics must be combined with customer, product, revenue, or operational data in Snowflake, BigQuery, or another supported data store. It is appropriate for repeatable reporting windows and governed historical loads.

Integration direction
Contentsquare
Martini
Snowflake or BigQuery
Example Mapping
Contentsquare FieldCanonical FieldTarget Field
projectanalyticsProjectIdproject_id
segmentsegmentIdsegment_id
metricmetricNamemetric_name
dimensiondimensionValuedimension_value
Martini implementation pattern

A scheduled workflow requests a defined project, segment, metric, dimension, and time window; polls an asynchronous export when required; validates time zones and schema; maps the response to warehouse tables; and upserts using a deterministic key derived from the export definition and reporting period. Transient API or downstream failures are retried, while permission and schema errors are routed for review.

Martini capabilities used
  • workflows
  • scheduled triggers
  • API consumption
  • data mapping
  • business rules
  • database or warehouse integration
  • error handling

Pattern 2: Prepare Contentsquare data for enterprise reporting

When to use this pattern

Use this pattern when Tableau or Power BI requires Contentsquare measures alongside commercial, CRM, or operational data. The workflow should publish a stable, reporting-ready model rather than expose product-specific API responses directly.

Integration direction
Contentsquare
Martini
Tableau or Power BI data source
Example Mapping
Contentsquare FieldCanonical FieldTarget Field
metricmeasureNameMeasure
page groupcontentGroupPage Group
projectpropertyIdProperty
reporting periodperiodStartPeriod Start
Martini implementation pattern

Martini retrieves selected metrics and dimensions, applies naming, aggregation, and time-window rules, and writes a normalized dataset to the customer’s selected reporting source. Validation prevents incomplete or incompatible dimensions from being published, and repeatable keys make reruns safe.

Martini capabilities used
  • scheduled workflows
  • REST API consumption
  • mapping and transformation
  • validation
  • business rules
  • monitoring

Pattern 3: Enrich Salesforce with aggregated experience insights

When to use this pattern

Use this pattern when approved, aggregated Contentsquare insights are useful in account, contact, campaign, or opportunity context. Avoid sending high-volume visitor-level analytics to CRM objects unless the data model and governance explicitly support it.

Integration direction
Contentsquare
Martini
Salesforce
Example Mapping
Contentsquare FieldCanonical FieldTarget Field
projectdigitalPropertyAccount Digital Property
metric valueengagementMeasureEngagement Indicator
page groupexperienceAreaExperience Area
reporting periodinsightPeriodInsight Period
Martini implementation pattern

A scheduled Martini workflow retrieves aggregated data, applies thresholds and field eligibility rules, resolves the Salesforce target, and creates or updates only approved objects. A deterministic project-period-insight key prevents duplicates, while failed CRM writes are retried only when transient.

Martini capabilities used
  • workflow orchestration
  • API consumption
  • data mapping
  • business rules
  • idempotency
  • error handling

Pattern 4: Create operational work items from analytics thresholds

When to use this pattern

Use this pattern when a validated Contentsquare metric or page-group condition should create or update a Jira issue, ServiceNow work item, or internal operations request. It is a polling-based pattern unless a specific Contentsquare callback is confirmed.

Integration direction
Contentsquare
Martini
ServiceNow or Jira
Example Mapping
Contentsquare FieldCanonical FieldTarget Field
page groupaffectedExperienceAreaAffected area
metric valueobservedValueObserved value
metric thresholdruleThresholdThreshold
export periodobservationWindowObservation window
Martini implementation pattern

Martini retrieves the relevant metrics, evaluates threshold and severity rules, enriches the work item with project and reporting context, and creates or updates the target item using an idempotency key. The workflow separates transient API failures from invalid queries and records the export identifier for troubleshooting.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • business rules
  • data transformation
  • idempotency
  • error handling
  • workflow monitoring

Applications commonly integrated with Contentsquare

Contentsquare data can be incorporated into broader analytics, reporting, CRM, and operational workflows. These relationships are integration patterns rather than evidence of native Contentsquare or Martini connectors, and product-specific support should be verified for the relevant edition.

Application Scenario Direction Martini Pattern
Salesforce Enrich account, contact, campaign, or opportunity context with approved aggregated digital experience and engagement insights. Contentsquare → Martini → Salesforce A scheduled Martini workflow retrieves selected metrics and dimensions, applies aggregation and eligibility rules, and updates approved Salesforce objects with deterministic keys to prevent duplicate records.
Adobe Analytics Compare or consolidate digital analytics data across web and digital properties into a broader measurement model. Adobe Analytics → Martini → Contentsquare Martini retrieves or receives data through the documented APIs of each system, normalizes dimensions and time windows, and writes a reconciled analytical model to a downstream store or reporting layer.
Google Analytics 4 Reconcile acquisition and behavioral analytics with Contentsquare experience metrics. Google Analytics 4 → Martini → Contentsquare Martini orchestrates API retrieval from the relevant systems, aligns reporting periods and dimensions, validates metric definitions, and publishes a combined dataset for analysis.
Snowflake Centralize Contentsquare exports with customer, product, and revenue data for governed analysis. Contentsquare → Martini → Snowflake A scheduler-triggered workflow requests a defined project and time window, polls asynchronous exports when required, maps results to warehouse tables, and performs idempotent loads.
BigQuery Store and analyze Contentsquare datasets alongside web, marketing, and product events. Contentsquare → Martini → BigQuery Martini retrieves documented API or export responses, converts them to the target schema, validates partitions and time zones, and writes the result using repeatable export keys.
Tableau Present Contentsquare metrics alongside operational and commercial data in enterprise dashboards. Contentsquare → Martini → Tableau Martini retrieves selected analytics results, applies business naming and aggregation rules, and stores or publishes a reporting-ready dataset for Tableau consumption.
Power BI Combine digital experience measures with CRM, finance, and operational reporting. Contentsquare → Martini → Power BI A Martini workflow produces a governed, normalized dataset from Contentsquare exports and makes it available through the customer’s selected Power BI-compatible data source.
ServiceNow Route validated digital experience issues or threshold breaches into incident, problem, or request workflows. Contentsquare → Martini → ServiceNow Martini periodically retrieves metrics, evaluates thresholds and deduplication rules, and creates or updates ServiceNow work items with an idempotency key.

How to build a Contentsquare integration in Martini

Objective

Configure the Contentsquare project identifiers and API credentials without embedding secrets in workflow definitions or source code.

Instructions in Martini

  • Create environment-specific configuration for project and workspace identifiers
  • Store the Contentsquare API credential in Martini Secrets Management
  • Use the authentication and request format documented for the selected Contentsquare API
  • Limit credentials to the projects and operations required by the integration

Objective

Select a scheduled workflow as the default trigger because general-purpose Contentsquare webhooks are not confirmed.

Instructions in Martini

  • Define the synchronization frequency and reporting windows
  • Use a callback trigger only if the selected Contentsquare product documents it
  • Store the last successful watermark or export identifier

Objective

Call the documented Contentsquare REST endpoint or initiate the required export for the selected project, metrics, dimensions, segments, and period.

Instructions in Martini

  • Build the request from validated project and query configuration
  • Support pagination, downloadable results, or asynchronous jobs where documented
  • Persist job, cursor, or continuation values when applicable

Objective

Coordinate export creation, polling, retrieval, validation, transformation, and delivery as a maintainable Martini workflow.

Instructions in Martini

  • Separate export submission from result retrieval when the API is asynchronous
  • Apply bounded polling delays and retry policies
  • Route permanent authentication, permission, and query errors for operational review

Objective

Convert Contentsquare-specific analytics responses into a canonical model suitable for warehouses, reporting platforms, CRM systems, or operational APIs.

Instructions in Martini

  • Map Projects, Segments, Metrics, Dimensions, Page groups, and Exports or reports explicitly
  • Normalize time zones, reporting periods, names, and optional fields
  • Validate required values before writing downstream

Objective

Apply governance, threshold, aggregation, and data-volume rules before sending analytics to downstream systems.

Instructions in Martini

  • Prefer aggregated insights when integrating with CRM or operational systems
  • Evaluate metric thresholds and severity rules where work items are required
  • Generate deterministic keys from the project, export definition, and time window

Common Contentsquare data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
ProjectsIdentify the Contentsquare workspace or analytics container associated with sites, applications, users, and data.Snowflake, BigQuery, reporting platforms, configuration storesMartini uses project identifiers as scoped workflow configuration and includes them in export keys, validation, logging, and target partitioning.
SegmentsDefine reusable groups of visitors or sessions using behavioral, demographic, technical, or other criteria.Data warehouses, reporting platforms, CRM analyticsMartini preserves segment definitions or identifiers with the extracted data and validates that the requested segment is available to the authorized project.
MetricsRepresent measures such as visits, sessions, conversion-related measures, engagement, and other experience analytics values.Snowflake, BigQuery, Tableau, Power BI, SalesforceMartini maps metric names and values to a canonical analytics model, applies validation and aggregation rules, and versions mappings when definitions change.
DimensionsGroup or filter analytics data by pages, devices, traffic sources, user segments, or other Contentsquare-defined attributes.Data warehouses, dashboards, operational APIsMartini normalizes dimension names and values, handles optional fields, and prevents unsupported or unexpected dimensions from silently entering downstream models.
Page groupsOrganize logical groups of pages for analysis and reporting.Reporting platforms, product operations APIs, data warehousesMartini retains page-group identifiers and labels, applies customer naming rules, and maps page-group results to reporting or threshold workflows.
Exports or reportsContain analytical results generated for a project, period, metric, dimension, and segment, potentially as asynchronous or downloadable results.Object storage, SQL databases, Snowflake, BigQuery, Tableau, Power BIMartini tracks export identifiers and status, polls when necessary, retrieves the result, validates the payload, and loads it idempotently.

Authentication and security considerations

Credential-based API access

Contentsquare API requests use an API credential associated with an account, project, site, or workspace. The exact header and credential lifecycle depend on the selected API product.

Protected configuration

Store Contentsquare credentials and project identifiers in Martini Secrets Management and environment configuration rather than workflow definitions or source code.

Permissions and data governance

  • Verify that the credential has access to the required projects and operations.
  • Treat behavioral, session, device, and user-related analytics as potentially sensitive.
  • Prefer aggregated data when sending insights to CRM or operational systems.
  • Do not assume OAuth 2.0, JWT, or named scopes without verifying the selected Contentsquare API.

Operational considerations for Contentsquare integrations

Rate limits and query cost

Confirm rate limits, quotas, concurrency limits, and project restrictions for the selected API. Avoid unnecessarily broad date ranges or granular dimensions, and partition large requests when required.

Pagination and asynchronous exports

Do not assume a single response contains the full dataset. Support documented pagination, cursors, downloadable files, or asynchronous job identifiers. Poll with bounded delays and handle failed, expired, or canceled exports.

Time windows and idempotency

Define the project time zone explicitly and use half-open reporting intervals to prevent overlap. Generate deterministic keys from the project, export definition, segment, metric, dimension, and period, then use upsert logic in the target.

Schema and operational resilience

  • Validate optional dimensions, metric availability, and required fields before loading data.
  • Version mappings when Contentsquare products, API versions, metrics, or dimensions change.
  • Retry transient rate-limit and network failures, but route permission and invalid-query failures for review.
  • Log project identifiers, export identifiers, periods, and correlation data without logging credentials or sensitive payloads.

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

Reusable orchestration

Martini separates Contentsquare API access, export polling, transformation, business rules, and delivery into maintainable workflows instead of embedding logic in one-off scripts.

Controlled data contracts

Martini can expose a normalized REST API so internal consumers do not need Contentsquare credentials or product-specific response knowledge.

Reliable processing

Scheduled execution, checkpoints, validation, deterministic keys, retries, and workflow logging provide operational controls that are difficult to maintain consistently across point-to-point scripts.

Flexible destinations

The same Contentsquare extraction pattern can deliver mapped results to databases, warehouses, reporting data sources, CRM systems, or operational APIs while preserving environment-specific configuration.

Frequently asked questions

How can Contentsquare be integrated with enterprise systems?

Contentsquare can be integrated through its documented REST APIs and analytics export capabilities. Enterprise workflows can retrieve project, segment, metric, dimension, page-group, and report data for defined periods, poll asynchronous exports when required, and deliver transformed results to warehouses, databases, reporting platforms, CRM systems, or operational APIs. General-purpose webhooks, public GraphQL APIs, SOAP APIs, and direct database access are not confirmed as standard mechanisms.

Can Martini integrate with Contentsquare?

Yes. Martini can integrate with Contentsquare by consuming its documented REST APIs, using API credentials stored in protected configuration, orchestrating scheduled retrieval or export workflows, transforming responses, and writing results to downstream systems. Martini can also expose a normalized REST API for internal consumers.

Do I need a connector to integrate Contentsquare with Martini?

No. A dedicated Contentsquare connector is not required. Martini can use Contentsquare’s confirmed native integration mechanisms, primarily its REST APIs, API credentials, documented exports, and any product-specific callbacks that are separately verified.

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

Lonti does not charge an additional per-connector or per-vendor fee to integrate Contentsquare. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Contentsquare, cloud infrastructure, databases, reporting platforms, or other third-party systems based on their subscriptions, usage, and deployment models.

Which Contentsquare integration methods should architects use?

REST APIs are the primary confirmed method. Batch, asynchronous, and downloadable exports are relevant for larger analytics datasets. Scheduled synchronization is the safer default when no documented callback is available. A public Contentsquare GraphQL API and current public SOAP API were not confirmed, so they should not be selected without product-specific verification.

Does Contentsquare provide webhooks or callbacks for analytics events?

General-purpose webhook coverage for all Contentsquare analytics events is not confirmed. Product-specific notifications or callbacks may exist in selected areas and must be verified for the relevant product and account. Otherwise, Martini can use scheduled workflows to poll for new exports or recently available analytics data.

How does Martini synchronize Contentsquare data incrementally?

Martini can use scheduled workflows with stored watermarks, repeatable project and export definitions, and half-open reporting windows. Deterministic keys and upsert logic make retries safe. Cursor-based or change-token synchronization was not confirmed, so incremental behavior should be based on the API’s documented export and query capabilities.

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

Martini can map Contentsquare objects and analytics values into canonical models, validate required fields, apply aggregation and threshold rules, and write to downstream systems. Workflows can distinguish transient failures from authentication, permission, or invalid-query errors, use bounded retries, log export identifiers and periods, and apply deterministic idempotency keys to prevent duplicate loads or work items.

Related Martini documentation

API integration

Workflows

Data processing

Security

Operations

Integrate Contentsquare with Martini

Use Martini to orchestrate secure Contentsquare API and export workflows, normalize analytics data, and deliver reliable results to the systems your enterprise depends on.

EXPLORE MARTINI
BOOK A DEMO