Skip to Content

Wiki source code of ONEcount Social

Last modified by Admin on 2025/06/27 12:14
Show last authors
1 {{details}}
2 (% class="wrapped" %)
3 |=(((
4 Target release
5 )))|(((
6 Release name or number
7 )))
8 |=(((
9 Epic
10 )))|(((
11 Link to related Jira epic or feature
12 )))
13 |=(((
14 Document status
15 )))|(((
16 (% class="content-wrapper" %)
17 (((
18 {{status title="DRAFT"/}}
19 )))
20 )))
21 |=(((
22 Document owner
23 )))|(((
24 (% class="content-wrapper" %)
25 (((
26 {{mention reference="XWiki.Admin" style="FULL_NAME" anchor="XWiki-Admin-SHRBE"/}}
27 )))
28 )))
29 |=(((
30 Designer
31 )))|(((
32 Lead designer
33 )))
34 |=(((
35 Developers
36 )))|(((
37 Lead developer
38 )))
39 |=(((
40 QA
41 )))|(((
42 Lead tester
43 )))
44 {{/details}}
45
46 == Goals ==
47
48 * Implement social tracking into ONEcount
49 * Tie tracking into existing and planned targeting
50
51 == Background and strategic fit ==
52
53 Currently we have analytics for banner, web e-mail, forms and transactions. We need an analytics screen for social
54
55 Most customers (both publishing and brand) use social advertising, targeting their audiences on other platforms. This gives us a way to target and track those audiences off-site as well as we do on-site.
56
57 == Assumptions ==
58
59 * Segments are created in the segment manager and pushed out to social network
60 * Clicks can be tracked by clicking on a URL on a ONEcount tracked site via cookie identification
61 * Impressions need to be tracked
62
63 == Requirements ==
64
65 (% class="wrapped" %)
66 |=(% class="numberingColumn" %)(% class="numberingColumn" %)
67 (((
68 #
69 )))|=(((
70 Title
71 )))|=(((
72 User Story
73 )))|=(((
74 Importance
75 )))|=(((
76 Notes
77 )))
78 |(% class="numberingColumn" %)(% class="numberingColumn" %)
79 (((
80 1
81 )))|(((
82 Segment creation
83 )))|(((
84 Segment creation needs to be standardized across all platforms
85 )))|(((
86 must have
87 )))|(((
88 * platforms: facebook, twitter, instagram, LinkedIn, DV360, Xandr (AppNexus)
89 )))
90 |(% class="numberingColumn" %)(% class="numberingColumn" %)
91 (((
92 2
93 )))|(((
94 Segment execution
95 )))|(((
96 Segments need to be pushed into social automatically
97 )))|(((
98 must have
99 )))|(((
100 FB,LinkedIn, etc., use hashed e-mails. DV360 and Xandr use linked cookies
101 )))
102 |(% class="numberingColumn" colspan="1" %)(% class="numberingColumn" colspan="1" %)
103 (((
104 3
105 )))|(% colspan="1" %)(% colspan="1" %)
106 (((
107 Segment Ananaylics
108 )))|(% colspan="1" %)(% colspan="1" %)
109 (((
110 Need a screen in ONEcount Analytics to show segment analytics; little red man drill-down to the who
111 )))|(% colspan="1" %)(% colspan="1" %)
112 (((
113 must have
114 )))|(% colspan="1" %)(% colspan="1" %)
115 (((
116 segment size (as pushed), impressions measured, clicks. Need to confirm that our numbers match the platform #s, or if there is a big difference, need to pull platform #s via API.
117 )))
118 |(% class="numberingColumn" colspan="1" %)(% class="numberingColumn" colspan="1" %)
119 (((
120 4
121 )))|(% colspan="1" %)(% colspan="1" %)
122 (((
123 Segment Name Sync
124 )))|(% colspan="1" %)(% colspan="1" %)
125 (((
126 Need to sync the segment name in ONEcount into the segment automatically
127 )))|(% colspan="1" %)(% colspan="1" %)
128 (((
129 \\
130 )))|(% colspan="1" %)(% colspan="1" %)
131 (((
132 \\
133 )))
134 |(% class="numberingColumn" colspan="1" %)(% class="numberingColumn" colspan="1" %)
135 (((
136 5
137 )))|(% colspan="1" %)(% colspan="1" %)
138 (((
139 Click tracking
140 )))|(% colspan="1" %)(% colspan="1" %)
141 (((
142 the campaign should have an identifier in the URL (ie., campid=SEGMENTNAME) so that when the user clicks on the banner, that URL is a page in the customer's site with this URL parameter. In our post-processing, we will grab all impressions with this parameter and store/track them under that segment's analytics
143 )))|(% colspan="1" %)(% colspan="1" %)
144 (((
145 \\
146 )))|(% colspan="1" %)(% colspan="1" %)
147 (((
148 \\
149 )))
150 |(% class="numberingColumn" colspan="1" %)(% class="numberingColumn" colspan="1" %)
151 (((
152 6
153 )))|(% colspan="1" %)(% colspan="1" %)
154 (((
155 View tracking
156 )))|(% colspan="1" %)(% colspan="1" %)
157 (((
158 We need a way to track banner impressions. One idea is to have a unique creative URL for each user (ie;, onecount.net/bannerA/OCID.jpg would be the URL for bannerA for user OCID). The OCID could be OCID, hashed e-mail, or whatever the platform supports. We will use URL rewriting the deliver the banner, and record impressions to onecount.net/bannerA/ocid.jpg as an impression for that user on that ad. I notice though that FB doesn't allow appending a unique identifier for each user to the URL or banner. IN that case, I am wondering if we should use a pixel (ie., onecount.net/bannnera.jpg) but use an IFRAME or JS to try to read the user's cookie when delivering the image. This is done by a lot of sites for reading/setting third-party cookies.
159
160 \\
161 )))|(% colspan="1" %)(% colspan="1" %)
162 (((
163 \\
164 )))|(% colspan="1" %)(% colspan="1" %)
165 (((
166 \\
167 )))
168
169 == User interaction and design ==
170
171 Wonder if we could use this in the image tag to read off of the OC domain: [[https:~~/~~/stackoverflow.com/questions/36318866/reading-a-cookie-from-a-different-domain>>url:https://stackoverflow.com/questions/36318866/reading-a-cookie-from-a-different-domain||shape="rect"]]
172
173 \\
174
175 == Questions ==
176
177 Below is a list of questions to be addressed as a result of this requirements document:
178
179 (% class="wrapped" %)
180 |=(((
181 Question
182 )))|=(((
183 Outcome
184 )))
185 |(((
186 Needs to be tested and validated so that our numbers match the platform numbers
187 )))|(((
188 Communicate the decision reached
189 )))
190
191 \\
192
193 == Not Doing ==
194
195 * List the features discussed which are out of scope or might be revisited in a later release.