Submission Interfaces

Data Submission Request

Purpose

The Data Submission Request is used to send tracking data to JENTIS.

This is the primary submission interface and should be used whenever:

• A tracking event occurs

• You want to forward tracking data to connectors via JENTIS

• Events originate outside the standard JENTIS Base Code setup

• Server-side events must be processed through JENTIS

This interface is intended for event-driven tracking use cases.

Typical Use Cases

• Purchase confirmations from backend systems

• Cancelled orders

• Subscription updates

• CRM-triggered events

• POS transactions

• Offline-to-online reconciliation

• Server-side event tracking

How It Works

1. An event occurs (e.g., purchase, cancellation, signup).

2. Your system creates an HTTP request.

3. The request is sent to the JENTIS Data Submission endpoint.

4. JENTIS processes the event.

5. Configured connectors receive the event based on your setup.

When to Use

Use the Data Submission Request if:

• You want to trigger connectors

• You want to track a measurable event

• You want the event to flow through the JENTIS processing pipeline

• You need deterministic, server-side tracking

Consent Submission Interface

Purpose

The Consent Submission Interface is used to submit consent decisions to JENTIS.

This interface is required when:

• You operate your own consent platform

• You do not use the JENTIS Base Code

• Consent decisions are collected outside the JENTIS environment

The goal is to:

• Transport consent decisions to JENTIS

• Store the consent status

• Ensure legal compliance

• Document which consent decision was active for which user

Typical Use Cases

• Custom CMP (Consent Management Platform)

• Native mobile app consent handling

• Headless frontend architecture

• Fully custom-built platforms

• Server-rendered applications without JENTIS Base Code

What Is Transmitted

The Consent Submission Interface sends:

• User identifier (if available)

• Consent categories / purposes

• Timestamp of consent decision

• Status (accepted, rejected, partial)

• Additional metadata if required

Legal & Compliance Relevance

Consent data stored via this interface enables:

• Auditability

• Legal proof of consent state

• Connector behavior control

• Transparency regarding active consent at a given time

It ensures that JENTIS:

• Knows the active consent status

• Can process tracking data lawfully

• Can document consent history

Key Difference Between the Two Interfaces

Interface	Purpose	Triggers Connectors	Legal Storage
Data Submission Request	Send tracking events	Yes	No
Consent Submission Interface	Send consent decisions	No	Yes

Decision Guide

Use the Data Submission Request if:

• You want to track an event.

• The event should be processed and forwarded to connectors.

Use the Consent Submission Interface if:

• You collect consent outside JENTIS.

• You need to store and manage user consent decisions in JENTIS.

• You want legally compliant consent documentation.

Important

Both interfaces require proper authentication and API access.

Please contact the JENTIS Helpdesk to receive:

• API credentials

• Endpoint documentation

• Technical onboarding support