This content has been marked as final. Show 7 replies
I think this is happening because you are just putting the word "test" as part of the name? Without knowing the specifics or how you're labeling these I think the best way to create test leads so they can easily be filtered is to make their company name = Test so that you they all belong to the same list and it's easier to pull.
You could test this now with those already created and see if it'd work.
Hope this helps!
I should work just on contains test. However what if it's a company that has the word "Test" in their name? You don't want to delete them. I previously had a list of 400 x-rated words to blacklist fake leads. However surprisingly how many names or company names partially match.
The forms that we have ask for Fname, Lname, Email and Tel No. as data entry fields so I'm only able to work with these to determine what are test sign ups.
If the word test exists in any other field i.e. Company then that's a user entry from an internal source and post-sign up so not much can be done there since it cannot be determined when someone decided to add the word test to the sign up profile. Hope that makes sense.
Plus as you say, someone later down the line could be genuine lead but didnt want to give the company name and added test.
I'll keep trying different strings to see if it picks up the leads I can see as clearly test sign ups.
Are only people from your company testing? If so you can limit to contains @companyname. of course. Or limit on ip-range. BTW we don't use test emails at all. Me and my colleagues just use our own company email addresses to test.
Yes, There's only about 4 people internally that can sign up as tests for website dev purposes including myself.
It gets complicated for us to use our actual company addresses as the sign up records get merged each time if the same email is used so the purpose of a test isn't as accurate if it's updating an existing record, so we would end up spending time deleting older tests before sign up. This kind of defeats the purpose of setting up an automated process to clean up test leads.
But what you're saying is that whenever anyone sets up a test lead, they must use a specific @companyname - in which case it can work because the first bit of the email address can be anything and so it wouldn't be looked as a duplicate lead and merged. - Is that right?
Yes indeed. I have a working filter for my lead life cycle campaign (for incoming leads) to exclude new leads containingen "@quintiq.com". This works perfectly. So you could create 2 filters:
Email Address / Contains / "@companyname.com"
Email Address / Contains / "test"
Now you can just use emails like: "firstname.lastname@example.org", "email@example.com", "firstname.lastname@example.org".
Sounds good to me. I will run some tests using this process and method - I'm confident it will work now :)
Many thanks for your feedback.