Econda

Econda is web analytics tool under the DYMATRIX brand. Using this destination, you can implement server-side tracking.

Key features

The Econda destination provides the following key features:

  • Events structure: our Events reference supports Econda event types, meaning that your data is properly bridged to the expected fields in an optimized way.

  • Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

  • Automatic hashing: information is automatically hashed matching partner specifications.

  • Smart mapping: data mapping can be readjusted using your datalayer defined fields.

  • Support for multi-item data: information included in the item array is dispatched to Econda.

  • Connection management: events are sent again in case of congestion or network issues.

Destination setup

Configuration

Settings
Description

Client Key

Required Your client key as reported in Econda interface under ConfigurationAnalytics JS Library .

Custom Event Mapping

Change the standard mapping between Econda event types and your events or add new mappings. See Quick reference for more details.

Custom Event Properties

Map your custom event properties by setting their field names in Econda property name and adding the values in Your value . In the column Your value path you should keep the default value Default (root) as it better fits most scenarios. In case you select either In "items" {items.X} or In "product" {items.X.product} , the Your value must be set with a property name and this destination will look for the provided property name starting from the items or product level respectively and set the value in Econda ec_Event .

Quick reference

Commanders Act Events
Econda Event Types

add_to_cart

c_add

add_to_wishlist

wlist_add

purchase

buy

view_item

view

[Any other event]

[No event type] [1]

[1] Other events are supported and no specific Econda event type is set.

Field Mappings

Most properties can be remapped using our "Smart Mapping" feature. For Econda, visits and sessions are the same and they are based on the distinct value count for the property sid. Additionally, Econda has a timeout set by default with 30 minutes, which can be changed, so even with the same sid the session counter will increase after the timeout has passed. Visitors are based on the property vid and its distinct count. An additional custom property retry_count is set with the number of send retries due to Econda endpoint congestion or connection interruptions.

Commanders Act Properties
Econda Properties

context.event_id

rid [*]

context.device.lifecycle.session_id

sid [*]

user.consistent_anonymous_id

vid [*]

context.page.location.hostname

host [*][1]

partners.econda.site_id

siteid [2]

partners.econda.category_path

content [3]

partners.econda.country_id

countryid [4]

context.device.lang

langid

partners.econda.order_process

orderProcess [5]

partners.econda.source

source

partners.econda.campaign

camp

partners.econda.privacy_mode

prv [6]

id

billing.0 [7]

user.id

billing.1 [7]

user.country user.city user.zipcode

billing.2 [7][8]

value

billing.3 [7]

See Econda Event Types in Quick Reference

ec_Event.0.type

items.X.id

ec_Event.0.pid

items.X.product.id

ec_Event.0.sku

items.X.product.name

ec_Event.0.name

items.X.product.price

ec_Event.0.price

partners.econda.category_path [9] items.X.product.category_1 [10]

ec_Event.0.group

items.X.quantity

ec_Event.0.count

search_term

search.0.0 [11]

search_results_number

search.0.1 [11]

context.device.ip

ip

context.device.user_agent

ua

user.email

hashedvalue [12]

Cookie TCAUDIENCE [13] DataSegments

usertype [14]

partners.econda.recipient_id

newsuid [15]

partners.econda.newsmid

newsmid [16]

partners.econda.target_group

Target.0 [17]

partners.econda.target_name

Target.1

partners.econda.target_value

Target.2

partners.econda.target_rule

Target.3

partners.econda.marker_name

marker [18]

partners.econda.onsite_cmp_seen1

icampv.0 [19]

partners.econda.onsite_cmp_seen2

icampv.1 [19]

partners.econda.onsite_cmp_seen3

icampv.2 [19]

partners.econda.onsite_cmp_click1

icampc.0 [20]

partners.econda.onsite_cmp_click2

icampc.1 [20]

partners.econda.onsite_cmp_click3

icampc.2 [20]

context.device.screen.width context.device.screen.height context.device.screen.zoom_factor

swsh [21]

user.id

login.0.0

user.login_success

login.0.1 [22]

video_title

media.0

event_name

media.1 [23]

cursor_position

media.3

total_length

media.4

partners.econda.tspageload

media.5

partners.econda.video_index_position

media.6

context.page.url

media.7

[*] Mandatory property. [1] If it's not provided, the "Smart Mapping" field Page URL (host) is used to retrieve the hostname. [2] the name of the website to be measured, as configured by DYMATRIX Support. This is usually the main domain, without the leading "www.". [3] A unique identifier for the content of the current website. By entering forward slashes ( / ), the website context (E.g. the path) can be transferred and analyzed in a summarized form at a later time. [4] The country identifier allows you to differentiate your website for different countries. [5] Here you can monitor the purchase process. A typical purchase process in an online store consists of several steps that the customer must complete before the purchase is completed. These include filling the shopping cart, entering billing information, etc. (E.g. 02_login ). [6] Privacy mode as defined in Econda. [7] Set when the Econda event type is buy . See Quick reference for more details. [8] Set with the value of the fields on the left and separated by the character forward slash ( / ). [9] Property used when Econda event types is view . [10] Property used when Econda event types is buy . [11] Set when a search event is triggered. [12] If provided in clear text, it's automatically hashed via SHA256. [13] More details are available following this LINK. [14] This two-dimensional array is set with the user segments provided. Priority on the left side. DataSegments must be a single dimension array with the user segment names provided at the index 0 and separated by the comma character. (E.g. ["USER_SEGMENT_NAME_1,USER_SEGMENT_NAME_2...."] ). [15] Newsletter recipient identifier as used in the ESP. [16] Newsletter identifier. [17] Target/goal group (E.g. newsletter subscription ) [18] Markers are measurement tools that allow you to place "light barriers" on a website. As soon as a visitor passes a light barrier, the contribution of this measurement point to achieving the defined goal is recorded and thus made transparent (E.g. SubscriptionClick). [19] With on-site campaigns, you use relevant areas of your website for sales-promoting marketing campaigns, e.g., in the form of on-site banners. Send the names of on-site campaign banners being seen (E.g. Summer Sale): you can send up to three names. [20] Send the names of on-site campaign banners being clicked (E.g. Summer Sale ): you can send up to three names. [21] E.g. 1280x1024|1.5 . [22] Set with 0 on sucessful login, otherwise 1 . Default value: 0 . [23] Supported video events Video Playback Started, Video Playback Paused, and Video Playback Completed: this property is set with either play, pause or ended respectively.

Last updated

Was this helpful?