Skip to Content
Last modified by Admin User on 2025/06/16 19:06
From version 1.1
edited by Admin User
on 2025/06/16 19:03
Change comment: Changed document syntax from [XWiki 2.1] to [xwiki/2.1].
To version 3.1
edited by Admin User
on 2025/06/16 19:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,0 +1,149 @@
1 +**How To Test Your Landing Pages/Pop-Ups**
2 +
3 +Testing your landing pages and pop-ups should be done prior to deployment. As part of the process, you’ll recognize that ONEcount behaves slightly differently depending on whether the user is “known” to ONEcount or not.
4 +
5 +This article outlines the best way to test your Landing Pages and Pop-Ups so that you can ensure a smooth user experience.
6 +
7 +We’ll use a simple e-mail acquisition pop-up in this example. In order for you and your team to test, you can either create a segment with your IP/Browser string in it, or target the pop-up at a non-public page on your web site.
8 +
9 +[[image:pop-up testing_723fa4937dd7d7d8.png||height="378" width="302"]]\\
10 +
11 +
12 +
13 +
14 +
15 +
16 +
17 +
18 +
19 +
20 +
21 +
22 +
23 +
24 +
25 +
26 +
27 +
28 +
29 +
30 +
31 +To start, let’s look at the four basic scenarios you will need to test.
32 +
33 +1) User is unknown to ONEcount, uses a “new” e-mail address (ie., one that is not already in the ONEcount database)
34 +
35 +2) User is unknown to ONEcount, uses an e-mail address that is already in the ONEcount database
36 +
37 +3) User is known to ONEcount, uses their existing e-mail address to subscribe
38 +
39 +4) User is know to ONEcount, uses a different e-mail address to subscribe
40 +
41 +
42 +1.
43 +11.
44 +111. (((
45 +=== Scenario #1: Unknown User/New Email ===
46 +)))
47 +
48 +Open an incognito window in your browser, or delete your ONEcount cookies (info on that can be found here). Visit the page where the pop-up will appear or load the landing page. Enter a New email address that is not on file, and hit submit.
49 +
50 +1.
51 +11.
52 +111. (((
53 +=== Scenario #1: Unknown User/Existing Email ===
54 +)))
55 +
56 +Open an incognito window in your browser, or delete your ONEcount cookies (info on that can be found here). Visit the page where the pop-up will appear or load the landing page. Enter a New email address that is not on file, and hit submit.
57 +
58 +[[image:pop-up testing_4e6acdde82f5f85e.png||height="375" width="297"]]
59 +\\
60 +
61 +
62 +
63 +
64 +
65 +
66 +
67 +
68 +
69 +
70 +
71 +
72 +
73 +
74 +
75 +
76 +
77 +
78 +
79 +
80 +
81 +
82 +
83 +At this point, you should be presented with a red box telling you that the email address you have entered is already in the system, and that a code has been sent to that address for verification. Enter the code in the box and hit submit. When you hit submit, ONEcount will “identify” your browser with the record containing that email address. This means that from this point on, ONEcount thinks you are this user.
84 +
85 +At this point, the pop-up should reload with your email in the box, ready to submit. If you are using a multi-question form, say for subscription or profile information, the information for the user whose email you are using should appear pre-populated in the form. You can now submit that form as the user whose email you entered.
86 +
87 +If you do not receive the e-mail, ONEcount has an option to Login or Lookup the user. This requires a Login/Lookup form, which can be configured within the system.
88 +
89 +[[image:pop-up testing_63487a4c11750aed.png||height="258" width="302"]]
90 +\\
91 +
92 +
93 +
94 +
95 +
96 +
97 +
98 +
99 +
100 +
101 +
102 +
103 +
104 +
105 +
106 +The Login/Lookup form allows you to use multiple data points to identify a user. You could use email or username and a password to log the user in. You could also use two pieces of non-volatile information about the person, say their account number and zip code. This allows you to identify users who are in your database who may not have an e-mail address in your database.
107 +
108 +Again, when the user logs in or identifies themselves, he or she is automatically “identified” by setting the appropriate ONEcount cookies, and taken back to the form, pop-up or landing page, which now appears with the user’s information pre-populated in the form.
109 +
110 +~*~**If you are identified or “known” to the system and you click on the Login/Lookup link, the Login/Lookup box will initially load, but when it sees the cookies are already set in your browser as an identified user, it will close and you will be returned to your pop-up or landing page. This is expected behavior.
111 +
112 +1.
113 +11.
114 +111. (((
115 +=== Scenario #3: Known User/Existing Email ===
116 +)))
117 +
118 +This is pretty straight-forward. Once you have completed steps #1 or step #2, your browser will have cookies set identifying you as a user in the system. Simply open the landing page or pop-up, and the email address you were identified with should appear in the email box. If your form has additional data points, those should be pre-populated with the information ONEcount has for your record. Simply submit the pop-up or landing page and you will be subscribed.
119 +
120 +1.
121 +11.
122 +111. (((
123 +=== Scenario #4: Known User/New Email ===
124 +)))
125 +
126 +Once you have completed steps #1 or step #2, your browser will have cookies set identifying you as a user in the system. Simply open the landing page or pop-up, and the email address you were identified with should appear in the email box. If your form has additional data points, those should be pre-populated with the information ONEcount has for your record. Change the e-mail address in the box, and submit the pop-up or landing page. You will be subscribed to the product, and the email address for the record you have on file will be changed to the address you entered in the box.
127 +
128 +1.
129 +11.
130 +111. (((
131 +=== Helpful Cookie Info For Testing ===
132 +)))
133 +
134 +ONEcount uses first-party cookies to identify users and track behavior. The easiest way to become “unknown” to ONEcount is to simply delete all of the cookies for the site you are on. This ensures that you will get a user experience like a first-time visitor. You can also use your browser’s incognito mode, but you will need to remember to close the incognito window each time you test.
135 +
136 +[[image:pop-up testing_7e0a1f8ef0333cbb.png||height="318" width="665"]]
137 +\\
138 +
139 +Here are the cookies that are most important while testing:
140 +
141 +~_~_tmpcookie: this identifies your browser as a user to ONEcount. Every person ONEcount sees gets a tmpcookie. If you do not have one, a new one will be created for you.
142 +
143 +~_~_ocid: this is a hashed token of your OCID, the unique identifier ONEcount uses for your record in its database. Having an ~_~_ocid cookie means ONEcount has identified you and will use the information associated with that hashed ID to pre-populate forms. To see what user your ~_~_ocid cookie hash represents, copy the value of ~_~_ocid from your browser, and in the ONEcount admin area, go to Miscellaneous → Hash Lookup. Paste the cookie value in the box and hit submit; the system will return the OCID of the user that ONEcount thinks you are
144 +
145 +~_~_ocation-~#~#~#~#: This cookie means that ONEcount has previously targeted you with an action from a segment. The segment were targeted by is represented by the id ~#~## after the dash. You can figure out which segment this is by going to the ONEcount admin area, Activation → Segment Manager. You will see a list of segments, with a GUID in the first column. Match the GUID to the ~#~## in the cookie and that is the segment that you have been targeted with.
146 +
147 +If you look at the expires column for this cookie, you will see that it expires in the lifetime of the segment target action. In other words, if the segment was set to target every day, the cookie will expire in 24 hours. If the segment is set to target weekly, the expire time will be 7 days. This is how ONEcount manages the frequency.
148 +
149 +If you would like to test the same action over and over again, simply delete the cookie tied to that action. In other words, if you are testing the action for segment #f3498090-67d1-4f18-b5b9-460c28539462, just delete the cookie ~_~_ocaction-f3498090-67d1-4f18-b5b9-460c28539462 from your browser and ONEcount will target you again.
pop-up testing_63487a4c11750aed.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.admin
Size
... ... @@ -1,0 +1,1 @@
1 +13.8 KB
Content