Requirements for Testing
Before launching a test, it’s important to ensure you have the right data and media setup in place. In this guide, we walk through the data and operational requirements for both GeoTests and Difference-in-Differences tests within Rockerbox.
🌍 Requirements for GeoTests
To run a GeoTest, you’ll need:
- KPI Data with Geographic Identifiers
- Conversion or lead data by date and location
- Acceptable geographic levels: Country, State, DMA, Zip Code
- Break out different conversion types if needed
- Data Availability in Rockerbox
- If using the Rockerbox Data Foundation, this may already exist in your Conversion tables
- If not, you may need to upload store-level or retail partner data (e.g., Amazon or in-store purchases), including store name, address, and date
- Media Buying Capabilities by Geography
- You must be able to target media at the same geo level as your test (e.g. State vs DMA)
- Digital media is typically easier to geo-target; affiliate, print, and influencer may pose challenges
🔁 Alternative: Difference-in-Differences Tests Without Geo Control
If you can’t control media geographically, Rockerbox can run a Difference-in-Differences test using attribution data.
Examples include:
- Brand vs. non-brand search
- Coupon strategy in one product category vs. another
In these cases, Rockerbox uses:
- Attributed conversions from your MTA tables
- Product-level purchase data from your Conversion tables