Close

Campaign & A/B Test FAQs

Why are my users getting wrong Content, or no Content at all?

There might be several reasons for this. Please check the following.

  • Does the user match the segment criteria?
    • If no, please set the segment criteria so that the right user will receive the right content.
    • If yes, please read on.
  • Check the API key and Channel ID of the Channel API request. If one of these is incorrect, the users can't get Content.
  • Channels have settings related to the message priority. The priority can be Random or by Priority. If you used the random setting, please review the related documentation in the Channel section.
  • Is the Campaign still active? Only active Campaigns provide Content.
  • Is the Message still active? Only active Content provide Content.
  • Is there custom targeting and scheduling for any Content? Check this from the campaign settings.
  • Is the content correct?

If none of these help, please contact Omniata Support.

Why are my results showing wrong data, or no data?

There might be several reasons for this. Please check the following.

  • Does the user match the segment criteria?
    • If no, please set the segment criteria so that the users are assigned to the Campaign.
    • If yes, please read on.
  • Check the API key and Channel ID of the Channel API request. If one of these is incorrect, the users can't be assigned.
  • Is the Campaign still active? Only active Campaigns assign users to campaigns.
  • Is there custom targeting and scheduling for any Content? Check this from the campaign settings.
  • Check the filters of the Results page.
  • Remember that a Data Point is not same as User. User active on two days counts as two data points.

If none of these help, please contact Omniata Support.

When does a user leave a Campaign?

The user leaves the test when the campaign finishes, but if content is still provided they will stay in the campaign. Once a Campaign ends no more users are included in the experiences.

If a Campaign is targeting new users, who are the new users?

New users are users who installed the application after the time of when the campaign is scheduled to begin. Please note that to receive Content, users must exist before it is sent. This means that a user must have sent, at a minimum, a single om_load event prior to the Channel API call to receive the Content.

When using segmentation, will a user still be in the Campaign when that users leaves the segment?

Yes. The user will remain in the Experience. A user is assigned to a experience in their user state if they qualify. The experience related user state does not change. So, once in a group always in a group.

How do I finish a Campaign?

Campaigns require an end date. Once the campaign is live, the end date cannot be modified.

To stop serving Content targeting users in a Campaign, you can always disable the messages from the associated channel.

Is it possible to move a user that belongs to an Experience of a Campaign to another Experience of that Campaign?

No, not possible. When a user is assigned to Experience of a Campaign, that assignment is permanent. The user can be assigned to other Campaigns, though. When the Campaign ends, user is no longer part of that Campaign.

Do I need to ensure that Push Notifications work without Omniata?

Yes. Delivering (sending all to way to a end user device) a push notification to iOS or Android is rather straightforward, the only requirements are the Device Token and Certification (in iOS) and GCM API Key and/or device Registration ID (Android) and the content. Omniata brings an additional layer of logic on top of the push notifications delivery. This is why it's important to test that the push notifications work before involving Omniata at all in the push notification delivery process. This is really important if you hit the case that you're not receiving push notifications from Omniata. Then you need to find out whether push notifications are working at all, meaning that you can send a push notification to your device without Omniata involvement.

iOS

Here's a brief guide on how to send push notifications to your device on iOS. First, you need to find out the Device Token. You can do this this programmatically by yourself, but it should be easier to follow the steps in the Integration section until your application is sending the Device Token to Omniata. Let the iOS SDK be in DEBUG mode (AndDebug:YES). Open the Panel in your browser and navigate to Settings > Model > Events. Now, when you install the application on your iOS device and start it up, there will be an event of Event Type om_apns_enable shown in the Event Console. Copy the value of the parameter om_device_token. That's your Device Token.

One of the easiest approaches to send a push notification is to use the Houston (https://github.com/nomad/houston) library. To install Houston, first install Ruby (https://www.ruby-lang.org) and then do 'gem install houston' or otherwise install Houston.

Now you have a command-line tool apn that can be used to send iOS Push Notifications. Type apn push --help for instructions. In practise to send a Push Notification to your iOS device, run the following code:

apn push -c PEM_FILE DEVICE_TOKEN  --alert "Alert test" --environment development

This code includes:

  • PEM_FILE is the location of your pem file
  • DEVICE_TOKEN is the iOS Device Token

You should now see a push notification on your device.

Ensure you're using the correct certificate (iOS)

From Local and Push Notification Programming Guide

To develop and deploy the provider side of a client/server application, you must get SSL certificates from the appropriate Dev Center. Each certificate is limited to a single application, identified by its bundle ID. Each certificate is also limited to one of two development environments, each with its own assigned hostname

The key takings:

  • Then bundleID of the certificate you upload to Omniata needs to exactly match the bundleID of your application
  • You'll have Development and Production certificates. In Omniata you need to upload the correct one. Most likely you'll upload both, in their correct locations:
    • Production certificate is used for the API Key(s) that you use in builds that you submit to App Store
    • Development certificate is used otherwise

I'm sending Push Notifications but don't see anything in Experiment Results?

There's an inherent delay because push notifications are delivered nightly and because Omniata's reporting works on daily basis.

Essentially when a push notification is sent on day 1, you'll see Experiment Results on day 2 after the nightly processing has finished. In practise when you start sending push notifications you don't see Experiment Results on the 1st day of when the push notifications are sent, but the following days.

What happens is the following:

  • Day 0: a user uses an application and Omniata stores his User State with certain values (e.g. country, revenue etc)
  • Day 1: after the nightly processing finished (in the early hours of the day UTC), Omniata decides to send a push notification to the user. He gets tagged to an Experience within a Campaign. Later that day (UTC day) the push notification is delivered to the user.
  • Day 2: on the early hours of the day (UTC), the nightly processing processed results of the Campaign related to the Push Channel and the Campaign results can be seen in the panel.

This article was last updated on February 25, 2016 22:36. If you didn't find your answer here, search for another article or contact our support to get in touch.

Contact Sales

Add Phone Number