First table:
Code:
tblProfileGrowth
ID |
Date |
Followers |
Impressions |
Reach |
160 |
20-Feb-20 |
|
114 |
58 |
159 |
19-Feb-20 |
5,396 |
1,991 |
995 |
154 |
18-Feb-20 |
5,387 |
1,819 |
977 |
155 |
17-Feb-20 |
5,387 |
2,115 |
1,214 |
156 |
16-Feb-20 |
5,386 |
1,349 |
797 |
157 |
15-Feb-20 |
5,376 |
2,024 |
1,335 |
158 |
14-Feb-20 |
5,370 |
1,636 |
923 |
153 |
13-Feb-20 |
5,357 |
|
|
152 |
12-Feb-20 |
5,349 |
2,408 |
1,175 |
151 |
11-Feb-20 |
5,336 |
1,846 |
1,275 |
146 |
10-Feb-20 |
5,332 |
1,642 |
1,093 |
147 |
9-Feb-20 |
5,331 |
3,266 |
1,895 |
148 |
8-Feb-20 |
5,330 |
2,195 |
1,173 |
149 |
7-Feb-20 |
5,314 |
3,948 |
1,294 |
Second table:
Code:
tblProfileInteractions
ID |
Date |
Profile Views |
Website Clicks |
LinkinBio Clicks |
LinkinBio Pageviews |
129 |
2020-02-20 |
9 |
0 |
|
|
128 |
2020-02-19 |
121 |
0 |
|
|
123 |
2020-02-18 |
82 |
0 |
|
|
124 |
2020-02-17 |
179 |
2 |
|
|
125 |
2020-02-16 |
159 |
0 |
|
|
126 |
2020-02-15 |
162 |
0 |
|
|
127 |
2020-02-14 |
194 |
1 |
|
|
122 |
2020-02-13 |
134 |
1 |
|
|
121 |
2020-02-12 |
134 |
1 |
|
|
120 |
2020-02-11 |
99 |
0 |
|
|
115 |
2020-02-10 |
120 |
2 |
|
|
116 |
2020-02-09 |
310 |
2 |
|
|
117 |
2020-02-08 |
183 |
1 |
|
|
118 |
2020-02-07 |
356 |
1 |
|
|
119 |
2020-02-06 |
129 |
1 |
|
|
QryProfileEngagement to join them:
Code:
SELECT tblProfileGrowth.Date, tblProfileGrowth.Followers, tblProfileGrowth.Impressions, tblProfileGrowth.Reach, tblProfileInteractions.[Profile Views], tblProfileInteractions.[Website Clicks]
FROM tblProfileGrowth, tblProfileInteractions
WHERE tblProfileGrowth.Date = tblProfileInteractions.Date
ORDER BY tblProfileGrowth.Date DESC;
Resulting query:
Code:
Date |
Followers |
Impressions |
Reach |
Profile Views |
Website Clicks |
20-Feb-20 |
|
114 |
58 |
9 |
0 |
19-Feb-20 |
5,396 |
1,991 |
995 |
121 |
0 |
18-Feb-20 |
5,387 |
1,819 |
977 |
82 |
0 |
17-Feb-20 |
5,387 |
2,115 |
1,214 |
179 |
2 |
16-Feb-20 |
5,386 |
1,349 |
797 |
159 |
0 |
15-Feb-20 |
5,376 |
2,024 |
1,335 |
162 |
0 |
14-Feb-20 |
5,370 |
1,636 |
923 |
194 |
1 |
13-Feb-20 |
5,357 |
|
|
134 |
1 |
12-Feb-20 |
5,349 |
2,408 |
1,175 |
134 |
1 |
11-Feb-20 |
5,336 |
1,846 |
1,275 |
99 |
0 |
10-Feb-20 |
5,332 |
1,642 |
1,093 |
120 |
2 |
9-Feb-20 |
5,331 |
3,266 |
1,895 |
310 |
2 |
8-Feb-20 |
5,330 |
2,195 |
1,173 |
183 |
1 |
7-Feb-20 |
5,314 |
3,948 |
1,294 |
356 |
1 |
6-Feb-20 |
5,283 |
2,542 |
1,541 |
129 |
1 |
5-Feb-20 |
5,271 |
2,093 |
1,295 |
208 |
0 |
4-Feb-20 |
5,255 |
2,942 |
1,882 |
191 |
2 |
3-Feb-20 |
5,253 |
2,319 |
1,236 |
248 |
0 |
2-Feb-20 |
5,245 |
2,202 |
1,282 |
234 |
2 |
1-Feb-20 |
5,235 |
2,271 |
1,023 |
232 |
4 |
I've truncated the data for space limits, but you get the idea. What I'd like is a chart that shows multiple of the fields in QryProfileEngagement. So far, I can only show Date on one axis (x) and followers (or one field) on y. Any way to have a single chart that shows, e.g., Followers, Impressions, Reach, and Profile Views all at the same time?