Testing With Beacons

1. Experience A/B Testing:

Note: Recommended for prospects or clients in the GroupBy Challenge (onboarding) phase.

You can use this form of A/B testing to test the effectiveness of GroupBy search in comparison to your existing search.

2. Rule A/B Testing:

Note: Recommended for GroupBy’s onboarded clients.

Tweak the GroupBy Search settings by creating different rules for various search types and compare their performance. For example, you can test if boosting a particular brand leads to increased conversion.

Experience A/B Testing

You can use this form of A/B testing to test the effectiveness of GroupBy search in comparison to your alternative search.

To perform this testing, you must include a gbi metadata with the value true at the top level of each beacon while setting up beacons for various event types.

Note: Add this metadata to all beacon types, not just Search.

Example with Search/Auto Search Beacon

Existing Search

Use the Search beacon type for a search performed by your existing search engine. For area, choose an area that matches the area you configured in Command Center.

sendSearchEvent Parameter
object
search
object

The search results.

required
metadata
string
required

GroupBy Search

For the search performed by GroupBy, use the AutoSearch beacon type, since you will not need to include search result details, only the search ID returned by GroupBy search.

sendAutoSearchEvent Parameter
object
search
object

Search properties for the Auto Search beacon.

required
metadata
array[object]
Note
  • Only one flag should be set by session. (either true or false). We recommend keeping the same experience for the same shopper across sessions.
  • Add this flag to all beacons sent per session, not just search, or they will not be processed correctly. For example, you need to tag product views, cart, and order events as well.