Overview
Different actions are needed depending on the campaign type. The next few sections explain how to respond to the various campaign settings. You should remember that FactFinder NG might return a number of campaigns.
It is also possible that not all of these campaigns will need to be handled in the same way (for example, several redirection campaigns). For this reason, it is important that you establish a priority for campaign types in your integration project. NG returns the campaigns in no particular order of priority.
Integrating Advisor Campaigns
These are campaigns for which the flavour attribute is set to ADVISOR. Advisor campaigns contain two new sections in their response:
The first section contains the active questions and associated answers.
The second section contains the complete question and answer tree. The active questions are those that are currently to be displayed to the shop visitor. Since the campaign consists of a tree or hierarchy of questions and answers, initially the “active” questions section consists of the first question in the tree.
When the user clicks a response, the follow-up questions below the selected answer are returned as active questions.
Integrating Feedback Campaigns
Feedback campaigns allow you to return text or products to the shop in the form of “feedback”. These campaigns are of the type (or flavour) FEEDBACK.
Feedback Text
Previous versions of FactFinder managed this sort of variable content using numbers. The integration project stipulated the position in the shop page at which specific feedback text numbers were to appear. The user then knew, for example, when creating feedback text number 3 that this text would appear in a specific location, such as above the search results [1].
Since version 6.7, names for the feedback text have been created and returned.
For current integrations, the names of the feedback text should be used as identifiers.
[1]
“Above the search results” in this instance really is simply an example. The position of the feedback text can be selected by the shop operator in the integration project.
The names are agreed with the shop operator during the integration project and configured accordingly in FactFinder. In the user interface, users can select from the predefined names.
In addition, you can specify whether or not each feedback text is able to contain HTML code. This characteristic is also returned by FactFinder along with the feedback text. It allows you to decide easily during the integration whether the text that is to be displayed should be html-escaped or not [2].
[2]
The default value for the HTML attribute is false. If the HTML attribute is not specified, this means that the feedback text may not contain HTML and must therefore be escaped.
Pushed Products
You can choose products for Feedback Campaigns. FactFinder returns the product list with the campaign.
The product list entries each contain the complete field list from the product record in the FactFinder database. However, in order to save bandwidth you can also pass the parameters
idsOnly=truewith the search request. In this case the content of the records is omitted.
It is possible for campaigns to be returned that contain 0 products. The user can select the option to integrate campaign products into the search results. In this case, no specific campaign product list is returned. However, a campaign is returned in order to indicate to the shop that a campaign has triggered on the search query.
Integrating Redirect Campaigns
If the campaign is a redirection campaign, the type is set to REDIRECT and the redirection field of the campaign is filled:
JSON: “flavour” and “target” within a campaignsList element.
A redirection consists of an optional name and a target URL. The URL is passed exactly as the user entered it (FactFinder does not perform any conversion on the URL).
When a redirection campaign triggers, the default reaction is that the current page automatically redirects to the specified URL. Other responses are also conceivable. For example, you could use redirection campaigns to provide shop visitors with links they can select. The name of the redirection can be used as the display text. The final decision on how to display the information is left to the shop operator in the integration project.