How to manage properties across multiple forms and reports
SOLVE
We're currently in the process of running a number of tests across different channels and webpages using forms.
We're looking to use similar properties across these forms but I am looking for advice on the best way to manage this from a CRM perspective.
I'll use an example scenario...
We run a test on Facebook where the user can opt to receive a brochure.
We then run an A/B test on our main website landing page with the following tests:
- Test A = The user can opt to receive a brochure
- Test B = The user can request a quote with a brochure
In order for us to report on the success on this, we'd build one custom property for 'Brochure request' which will then be applied across each form and added to reports along with the form submission filter.
My concern is, though, that the user might submit the Facebook form and request a brochure, but then go on the website and submit the form for Test A. Then, because they have populated the brochure property on the Facebook form, then it will be showing as populated in the Test A report, even though they didn't request a brochure from that form.
Historically, we have created new properties for new tests, but my concern is that this will create a huge mess in the CRM as time goes on and may not be the most practical way around it.
Does anyone have any suggestions on how best to approach this?
Instead of using custom properties to track this, what I'd recommend is having your landing page update to use separate forms for Variant A and Variant B. Then you could run reports based on form submissions where you would know that the leads would have filled out the forms in your test groups regardless of what their properties say. This would also be much more sustainable as you conduct more tests so that you don't create too many custom properties.
If you're using HubSpot landing pages, using the A/B test feature can accomplish this easily by just swapping out the hubspot forms you use for each variant. If it's hosted elsewhere, a tool like Google Optimize should also do the trick.
Instead of using custom properties to track this, what I'd recommend is having your landing page update to use separate forms for Variant A and Variant B. Then you could run reports based on form submissions where you would know that the leads would have filled out the forms in your test groups regardless of what their properties say. This would also be much more sustainable as you conduct more tests so that you don't create too many custom properties.
If you're using HubSpot landing pages, using the A/B test feature can accomplish this easily by just swapping out the hubspot forms you use for each variant. If it's hosted elsewhere, a tool like Google Optimize should also do the trick.
