/
Invoke Rule

Invoke Rule

Rules built within Alterian Journey Orchestration can be very comprehensive. In some scenarios however you gain efficiencies in design and effort by building Rules that themselves call other Rules.

Our Public Rule - Track Web Conversion uses this functionality via the Invoke rule Public Template.

The Invoke rule Public Template will take the fields that flow into it and create a file (in JSON format) that contains the fields and their corresponding values.

Next you to specify another Rule within your Client (and Target) to pass the file to.

The Rule accepting the file is configured via a parameter in the Invoke Rule Public Template.

The Rule accepting the file needs to start with a Realtime input to accept the file and to then split the file into its constituent parts. The Realtime Input Public Template will split out the Standard Alterian CX fields.

If you have created bespoke fields further Tiles may be required to allow these further fields to be decoded into the Rule.

The read conversion fields Public Template will split out the Conversion fields generated by the Category Lookup Public Template allowing them to be used in the Rule. This is used in the Track Web Conversion Public Rule.

Input Data

Field

Description

Example

Field

Description

Example

 

 

 

Field Mapping

No Fields to map the Invoke Rule takes all fields.

Configuration

 

Field

Description

Example

Field

Description

Example

DDE_Client

This is the Client that the Rule is currently Running in.

demord, AcadianTravel

DDE_Target

This is the Target that the Rule is currently Running in.

Dev, Prod, Test

rule name

Which rule in the client and target specified above should receive the file created by this Rule

track-conversion

Output Fields

Field

Description

Example

Field

Description

Example

 

 

 

Related content