What does the colour of the cloud icon mean?
Each event has a cloud just before the event name. The cloud icon can be of 3 colours.
Grey icon means that the event does not sync with the profiles in Profile Cloud i.e. no data is stored in Profile Cloud. This setting is managed in each created event. “Option” à “save to profile”. See below screenshot.
Blue icon means that the event is synced with the profiles in Profile cloud i.e. event is stored in the profiles in Profile Cloud.
Yellow cloud means that the event cannot be synced with Profile Cloud because of disabled permissions on either section or bucket level.
- The section does not allow any data to be synced with cloud.
- The bucket permission has “profile.update” disabled for the Web Data Collection App.
Changes in development mode are applied immediately. If you are browsing your website in development mode (using the APSIS bookmarklets), you should, therefore, see your changes directly.
When you deploy a version to live, it can take up to 10 minutes for the changes to be applied to your website. This is because APSIS uses caching for efficient delivery.
If your changes are not applied it can be due to your browser caching the content. Try to clear browsing data and test again.
The first step in creating a new tag is to choose a vendor. If the vendor you are looking for is not present in the app store, it must be created. To do this, follow the steps below.
1. Under each category of apps, there is an option to “Add vendor”. Choose the category of your choice and click on “Add new”.
2. Click on “Read more” and give the app a descriptive name, presumably the name of the vendor, select a category and click “Install”.
3. The tag has now been created but it is empty, which means that the specific vendor script needs to be inserted. Do this by clicking into the app and click on “the tab “Tags” and “New tag”. In some cases, a vendor has more than one script, therefore give each script a descriptive name.
4. Once you have clicked on “New tag” the following code editor screen will appear, which is the area where the script should be inserted.
- On this page, you will see argument types displayed on the left-hand side of the screen. You can use the arguments - Boolean, Integer, String, Object and Array - by double-clicking on the desired argument in the left-hand menu. These argument types are used to add extra functionalities to the building block (shown below). Some vendors require dynamic/input parameters such as an order ID or a customer ID. By using these arguments the building block will show these features when used in an event.
Example of a created tag in the event builder console.
5. Click on an argument type in the left-hand menu. The argument will appear above the code editor.
6. Double click on the desired argument.
- The following screen will appear. Fill in the options. Each of the fields are explained in more details below:
DEFINITIONS OF FIELD NAMES FROM ABOVE IMAGE:
- Codename is the name that will appear above the code editor. When you click on it the value will be inserted in the script.
- Display name is the name that the option will show in the building block when used in a rule.
- Value Type is the type of value for this argument. It can either be a static value to be set once or a dynamic value, for example, product name or price.
- Option is only available for boolean, integer and string. This is needed if you want to display a dropdown list with pre-defined options to select while you are building a rule. Use a comma to separate the values that you want to display.
Example of a building block using the “Option” field
- Required is used to set whether this information is required to be filled out when creating a rule or optional.
- Default value is an option to set a value in cases where the intended value is not populated.
- Description is a free text option to describe what the building block is used for. It will appear as a question mark in the building block as shown below.
When you saved your tag you will now be able to access it under the main navigation icons and in the event builder area under the category “tags”.
- Open the dropdown list in the upper right corner, Click on “bucket list”.
- Now you will get to the list with all the existing buckets. Click on “Create new bucket”
- Give your bucket a name.
- An ID is generated by Profile Cloud (Only for technical users). Profile Cloud identifies and allows access to this bucket by this ID.
- Optional description field.
The APSIS interface is optimized for modern versions of Google Chrome, Firefox and Safari. For the best possible experience, we recommend using one of these browsers.
To verify if this is the case, just go to the sign-in page: a notification will be displayed if your browser is not one of the recommended ones.
When events have been created and tested they will remain idle until deployed in APSIS.
- Deploy the events by open the APSIS web data collection app, and go to the Deploy-tab.
- Click on the Deploy button
- Add a Description in order to make sure the organization understand and keep track of the changes that have been done.
The comment typed will be displayed here
If anything, unwanted happens after the deploy, there is a possibility to withdraw the deploy and restore to the previous version. Simply click on the “restore to Dev” button.
Event data are a type of building blocks. Their purpose is to define data values. It can be data about the visitor, the page, the session, the traffic source etc.
- Click on the app store icon
- Search or click through to the desired app.
- Click on “read more”
- If your organization has access to the desired app, just click install and it will appear under the correspondent category in the top navigation bar. If your organization does not have access, click on “Contact Us” and an APSIS representative will contact you.