Post-conversion

Dymatrix docs: https://docs.econda.de/en/MONDE/reports/vordefinierte-analysen/marketing.html

What is Dymatrix (Econda) post-conversion?

"A post-conversion takes place when a visitor first visits your online shop via a campaign, but the conversion (i.e. the purchase) does not take place during the current visit but at a later point in time. This happens very often, for example with high-priced products."

Please note for post-conversion:

• Post-conversion follows the Last-touch attribution: Therefore, if a visitor visits your site through a keyword ad, does not make a purchase initially, but returns two days later through another source, e.g, a campaign, and makes a purchase the day after, this post-conversion is attributed to the campaign, not the keyword ad.

• The default post-conversion period considered is 30 days. Any conversion after the 30 days will not be credited to the campaign.

Post-conversion implementation in JENTIS (cookieless)

By defaults post-conversion is turned off in the Dymatrix connector in JENTIS. You can find this setting by opening the connector and opening the Optional Constants where there are 2 fields.

• "Post-conversion attribution mode": Check this toggle on, if you would like to activate this feature.

• "Post-conversion list": This field contains the default number of days for each source type for the post-conversion. You can modify this list, in case you would like to activate post-conversion for only certain source types, or if you would like to change the 30 day default value for any of them.

  • Dymatrix sources: Affiliate (affiliate), Campaigns (cp), Cooperation (coop), Display (display), E-Mail (nl), Mobile (mobile), Paid Search (kw), Paid Social (paidsocial), Print (print) and Retargeting (retarget)

  • Value Format: "affiliate:30,cp:30,coop:30,display:30,nl:30,mobile:30,kw:30,paidsocial:30,print:30,retarget:30"

  For sources not present on the list, Dymatrix will work as if post-conversion was not turned on.

In JENTIS post-conversion does not use cookies to track the visitors' last touchpoint, but instead stores this information in its own storage up to number of days defined.