Here is what shipped in September, plus a few updates from late August that belong in the same picture.
- Data Enrichment for App-Tracking traffic: the enrichment plugins you use for web data now apply to events sent through the JENTIS App SDK.
- Changelogs filtered to your published version: the container changelog shows only changes that affect what is live, and you can compare two versions directly.
- Fuzzy search in the DCP: find tags, variables and settings without typing the exact name.
- Connector updates: Amazon Ads Events API with all standard and custom events, Reddit Conversions API version 3, and three DYMATRIX extensions.
Data Enrichment now covers App-Tracking traffic
Enrichment plugins add data from external systems to an event after it reaches the JENTIS server: product attributes from a feed, location data derived from the IP address, or customer attributes from a login endpoint. Until now this applied to events captured on the web. As of 15 September, the same plugins process Data Submission requests sent through the JENTIS App SDK for iOS and Android.
The enrichment runs on the JENTIS server, so the SDK stays small and the app does not call external APIs itself. Your connectors receive the enriched variables from app events the same way they receive them from web events, and one enrichment configuration serves both channels.
How it works in the SDK
The SDK offers two commands. addEnrichment() reuses data your app has already pushed into the tracking chain, so you do not pass the same values twice. addCustomEnrichment() takes static, predefined values. Either command is called before .submit(). This needs app development work, and Data Enrichment itself is activated per account by your account manager. The App Tracking documentation has code examples for both platforms.
Changelogs that show only what affects your published version
Container changelogs in the DCP now list only the changes that are relevant to the published container version, based on the version's active dependencies. Changes to elements the published version does not depend on no longer appear in the list. The result is a changelog you can read as a record of what actually changed on your site.
Alongside the filter, new version-to-version comparison tools let you select two container versions and see the differences between them. This is useful before a publish, when you want to confirm what will go live, and afterwards, when you need to trace when a change was introduced.
Fuzzy search across the DCP
Search fields in the DCP now use fuzzy matching. A typo, a partial name or a different word order still returns the tag, variable or setting you are looking for, and results are ranked by relevance, so the closest match comes first. This applies to the search fields throughout the platform.
Connector updates
Amazon Ads: all standard and custom events through the Events API
The Amazon Ads connector uses the Amazon Ads Events API (CAPI v2) to send conversions server-to-server. As of 10 September it supports all standard and custom Amazon events, and it passes the ipAddress property with each event. You can measure off-Amazon conversions such as purchases and add-to-cart events from your own website in Amazon Ads and use them for attribution and audiences.
Authentication is handled by the connector. Amazon's access tokens expire after one hour, so the connector generates and refreshes them in the background. You provide your Login with Amazon client ID and secret once, together with either an existing refresh token or a one-time authorization code, plus your advertiser account ID and regional API endpoint. Setup details are in the Amazon Ads documentation.
Reddit: Conversions API version 3
The Reddit connector now includes tag templates for version 3 of Reddit's Conversions API. Version 3 supports custom events across the funnel and improves match rates on Reddit's side. A dedicated ViewContent template handles article and listing pages that carry no product data, which matters for publishers and content sites.
Migration is manual: install the version 3 tags and deactivate the version 2 tags in your container, as described in Reddit's documentation. The version 2 templates remain available until you switch.
DYMATRIX: Click-Monitor, AI search detection and extended post-conversion attribution
DYMATRIX received three updates. The new Dymatrix Click-Monitor connector can be installed next to the existing Dymatrix Analytics connector, and the two work together without extra configuration. The connector now also detects visits that originate from AI search tools and passes that information to DYMATRIX. And the post-conversion attribution request carries additional fields, which you enable directly in the connector configuration.
Taken together, website interaction data reaches your DYMATRIX platform in real time with more context per event, which is what DYMATRIX needs to run personalised user journeys. Setup is in the DYMATRIX documentation.
And that's September
Questions about any of these updates? Contact your account manager or reach us through the Helpdesk.
Every entry, with dates and bug fixes, is in the Release Notes & Changelog.
