Adding Communications tables for Campaign Objectives

Campaign Objectives in Orbit require response attribution.

In order to report on this, the FastStats system needs to have the standard PeopleStage/Campaign tables included.

 

You can add these to an existing design by using the Merge functionality within Designer.

 

To get the design with the required tables, you need to download the WebService.zip file for the relevant release.

 

The design is located within WebService\FastStatsServer\PeopleStage Resources\FastStats Standard PS Design\ and is named

To add these tables to an existing design:

 

1. Locate the ‘PeopleStage Standard Design.xml’ file in the WebService.zip file.

2. You might need to extract and copy this .xml file onto the build machine.

3. Open your design file using FastStats Designer

4. From the File menu choose Merge

5. Use the Browse button to browse to the .xml which contains the tables to merge

6. Leave the Merge Post-load actions option checked

7. Click the Merge button

You will need to join the Communications table to the relevant Contact Id in your design.

 

It will also amend the following Post Load Actions:

If you are not using the standard tables then you will need to tag the equivalent tables and variable names.

 

To tag a table, right-click on the table header with Table Relationships and choose Properties

Enter the tag name into the Tags textbox and click OK

To tag a variable, go to Define Variables

Click in the Tags textbox

Click the ellipsis button which appears and then enter the tag into the resulting dialog box:

Click OK

 
If you are not using the supplied PeopleStage Standard Design.xml design then you will need to tag certain tables and fields.

 

Tables that need tagging

 

 

Your equivalent Communications table needs tagging as Communications

Your equivalent Responses Attributed table needs tagging as AttributedResponses

Your Email Responses table needs tagging as EmailResponses

 

Fields that need tagging

 

Date of Communication equivalent needs tagging as CommunicationDate (Communications table)

Cost of Communication equivalent needs tagging as CommunicationCost (Communications table)

The Communication Channel needs tagging as CommunicationChannel (Communications table)

The Messages needs tagging as CommunicationMessage (Communications table)

The Campaign Name needs tagging as CampaignName (Communications table)

The Control field needs tagging as CommunicationControl (Communications table)

The Attributed Response Type needs tagging as ResponseType (AttributedResponses table)

The Percentage Attributed needs tagging as ResponsePercentage (AttributedResponses table)

Response Revenue needs tagging as ResponseRevenue (AttributedResponses table)

The Response Date needs tagging as ResponseDate (AttributedResponses table)

The Response Event Trigger Date needs tagging as EmailResponseDate (EmailResponses table)

The Email Response Type needs tagging as EmailResponseEvent (EmailResponses table)

• Related Articles

• Creating a Second Orbit Updater

  Some partner configurations will have more that one Orbit installation. This article describes the process for setting up additional Orbit Updaters to allow side by side Orbit installations on a single web server. This guide assumes that Orbit is ...

• Combining Table Results in Orbit using a CubeLookup Expression

  Sometimes it is useful to be able to get results from a Table in Orbit and use them in another Table. Within Orbit, it isn't currently possible to refer to results in one tile within another one. However, we can use a combination of some powerful ...

• PS Unable to find the versioned file

  In Q3 23 we changed the default stance on versioned selections to error if it can not find the latest version available for the selection that is being used in the Campaign. To revert this back to use versioned files in the db, please set this in the ...

• One Per Aggregations in PeopleStage

  One Per Aggregations in PeopleStage are useful when you want to campaign to a Person level but output transactional fields. For example, in our Holidays demo data, we have a Bookings table which is transactional to the Person table. We might want to ...

• Row Filter Selection Logic

  When defining Row Filters in Orbit, you need to define the selection filters all the way up the hierarchy for consistent results and to avoid any errors. To explain this, let's say you have a table structure of: Households (Region) |____ People ...