You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/auxia.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,9 @@
1
1
## Auxia
2
+
2
3
Auxia is a service that uses ML models to optimise messaging.
3
4
4
5
We use it in support-dotcom-components. Currently there are two uses:
6
+
5
7
-[Sign-in gate](signinGate.md)
6
8
- Banners
7
9
@@ -12,9 +14,11 @@ support-dotcom-components uses the API to find out if a message should be displa
12
14
## Uses
13
15
14
16
### Sign-in gate
17
+
15
18
[See separate doc.](signinGate.md)
16
19
17
20
### Banners
21
+
18
22
We are trialling using Auxia for banner decision making.
19
23
20
24
In the first experiment we ask Auxia whether or not to suppress the banner. If Auxia does not suppress the banner then we use the existing rules.
@@ -26,3 +30,11 @@ Auxia is consulted when the `enableAuxiaForBanners` switch is on, a browserId is
26
30
If Auxia is consulted and a banner is returned then we also track events on the client using Auxia's `LogTreatmentInteraction` endpoint. We proxy these requests via `/banner/interaction`.
27
31
28
32
See [auxia.ts](../src/server/lib/auxia.ts) for implementation.
33
+
34
+
### Gandalf bypass
35
+
36
+
While the `enableGandalfSignInGate` channel switch is on, New Zealand readers
37
+
are never sent to Auxia for sign-in gates: the journey is fully
38
+
Guardian-managed (see [signinGate.md](signinGate.md)). Banner behaviour is
39
+
unchanged — the banner suppression checker consults Auxia exactly as before,
DCR article pages make a request to SDC's `/auxia/get-treatments` endpoint. This endpoint may return a "treatment", which is the configuration for a gate.
9
11
10
12
SDC will decide which treatment (if any) to return based on either:
13
+
11
14
1. An API call to Auxia, for browsers which are eligible and consented,
12
15
2. Hardcoded config in SDC, for all other browsers
13
16
@@ -19,7 +22,38 @@ For details of the current configuration, see [logic.md](/src/server/signin-gate
19
22
20
23
SDC also has an endpoint for tracking interactions (view/click) with the gate: `/auxia/log-treatment-interaction`. These events are forwarded on to Auxia, and are independent of the standard Ophan tracking.
// "Gandalf" is the marketing name for the Guardian-managed sign-in gate
131
+
// journey: a 100% rollout run entirely by Guardian rules with no Auxia
132
+
// involvement (currently New Zealand, gated by the enableGandalfSignInGate
133
+
// channel switch).
134
+
//
135
+
// The Guardian-managed hard gate. The copy matches guMandatoryUserTreatment,
136
+
// but the treatmentType uses the POPUP variant so the client renders the v2
137
+
// modal (mounted on document.body) instead of the inline article gate.
138
+
//
139
+
// The treatmentId is Gandalf-specific (not the shared
140
+
// 'default-treatment-id') so Ophan component events for the Gandalf popup
141
+
// are distinguishable in analysis. Auxia interaction suppression does not
142
+
// depend on the treatmentId: the client skips Auxia calls for responses
143
+
// carrying the gandalfSignInGate marker.
144
+
145
+
consttitle="No, you don't need to pay to keep reading";
146
+
constsubtitle="Simply sign in - it's free, and much quicker than you think";
147
+
constbody=
148
+
'We’re committed to keeping our quality reporting open. By registering and providing us with insight into your preferences, you’re helping us to engage with you more deeply, and that allows us to keep our journalism free for all.';
0 commit comments