forked from segmentio/Analytics.NET
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathClient.cs
More file actions
679 lines (599 loc) · 26.9 KB
/
Client.cs
File metadata and controls
679 lines (599 loc) · 26.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
using System;
using System.Collections.Generic;
using System.Threading.Tasks;
using Segment.Flush;
using Segment.Model;
using Segment.Request;
using Segment.Stats;
namespace Segment
{
/// <summary>
/// A Segment.io .NET client
/// </summary>
public class Client : IDisposable
{
private IFlushHandler _flushHandler;
private string _writeKey;
private Config _config;
public Statistics Statistics { get; set; }
#region Events
public delegate void FailedHandler(BaseAction action, System.Exception e);
public delegate void SucceededHandler(BaseAction action);
public event FailedHandler Failed;
public event SucceededHandler Succeeded;
#endregion
#region Initialization
/// <summary>
/// Creates a new REST client with a specified API writeKey and default config
/// </summary>
/// <param name="writeKey"></param>
public Client(string writeKey) : this(writeKey, new Config()) {}
/// <summary>
/// Creates a new REST client with a specified API writeKey and default config
/// </summary>
/// <param name="writeKey"></param>
/// <param name="config"></param>
public Client(string writeKey, Config config)
{
if (String.IsNullOrEmpty(writeKey))
throw new InvalidOperationException("Please supply a valid writeKey to initialize.");
this.Statistics = new Statistics();
this._writeKey = writeKey;
this._config = config;
IRequestHandler requestHandler = new BlockingRequestHandler(this, config.Timeout);
IBatchFactory batchFactory = new SimpleBatchFactory(this._writeKey);
if (config.Async)
_flushHandler = new AsyncFlushHandler(batchFactory, requestHandler, config.MaxQueueSize);
else
_flushHandler = new BlockingFlushHandler(batchFactory, requestHandler);
}
#endregion
#region Properties
public string WriteKey
{
get
{
return _writeKey;
}
}
public Config Config
{
get
{
return _config;
}
}
#endregion
#region Public Methods
#region Identify
/// <summary>
/// Identifying a visitor ties all of their actions to an ID you
/// recognize and records visitor traits you can segment by.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.</param>
///
/// <param name="traits">A dictionary with keys like "email", "name", “subscriptionPlan” or
/// "friendCount”. You can segment your users by any trait you record.
/// Pass in values in key-value format. String key, then its value
/// { String, Integer, Boolean, Double, or Date are acceptable types for a value. } </param>
///
public void Identify(string userId, IDictionary<string, object> traits)
{
Identify(userId, traits, null);
}
/// <summary>
/// Identifying a visitor ties all of their actions to an ID you
/// recognize and records visitor traits you can segment by.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.</param>
///
/// <param name="traits">A dictionary with keys like "email", "name", “subscriptionPlan” or
/// "friendCount”. You can segment your users by any trait you record.
/// Pass in values in key-value format. String key, then its value
/// { String, Integer, Boolean, Double, or Date are acceptable types for a value. } </param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Identify(string userId, IDictionary<string, object> traits, Options options)
{
if (String.IsNullOrEmpty(userId) && !HasAnonymousId(options))
throw new InvalidOperationException("Please supply a valid userId to Identify.");
Enqueue(new Identify(userId, traits, options));
}
#endregion
#region Group
/// <summary>
/// The `group` method lets you associate a user with a group. Be it a company,
/// organization, account, project, team or whatever other crazy name you came up
/// with for the same concept! It also lets you record custom traits about the
/// group, like industry or number of employees.
/// </summary>
///
/// <param name="userId">The visitor's database identifier after they log in, or you know
/// who they are. By explicitly grouping a user, you tie all of their actions to their group.</param>
///
/// <param name="groupId">The group's database identifier after they log in, or you know
/// who they are.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Group(string userId, string groupId, Options options)
{
Group (userId, groupId, null, options);
}
/// <summary>
/// The `group` method lets you associate a user with a group. Be it a company,
/// organization, account, project, team or whatever other crazy name you came up
/// with for the same concept! It also lets you record custom traits about the
/// group, like industry or number of employees.
/// </summary>
///
/// <param name="userId">The visitor's database identifier after they log in, or you know
/// who they are. By explicitly grouping a user, you tie all of their actions to their group.</param>
///
/// <param name="groupId">The group's database identifier after they log in, or you know
/// who they are.</param>
///
/// <param name="traits">A dictionary with group keys like "name", “subscriptionPlan”.
/// You can segment your users by any trait you record. Pass in values in key-value format.
/// String key, then its value { String, Integer, Boolean, Double, or Date are acceptable types for a value. } </param>
///
public void Group(string userId, string groupId, IDictionary<string, object> traits)
{
Group (userId, groupId, traits, null);
}
/// <summary>
/// The `group` method lets you associate a user with a group. Be it a company,
/// organization, account, project, team or whatever other crazy name you came up
/// with for the same concept! It also lets you record custom traits about the
/// group, like industry or number of employees.
/// </summary>
///
/// <param name="userId">The visitor's database identifier after they log in, or you know
/// who they are. By explicitly grouping a user, you tie all of their actions to their group.</param>
///
/// <param name="groupId">The group's database identifier after they log in, or you know
/// who they are.</param>
///
/// <param name="traits">A dictionary with group keys like "name", “subscriptionPlan”.
/// You can segment your users by any trait you record. Pass in values in key-value format.
/// String key, then its value { String, Integer, Boolean, Double, or Date are acceptable types for a value. } </param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of the message.</param>
///
public void Group(string userId, string groupId, IDictionary<string, object> traits, Options options)
{
if (String.IsNullOrEmpty(userId) && !HasAnonymousId(options))
throw new InvalidOperationException("Please supply a valid userId or anonymousId to call #Group.");
if (String.IsNullOrEmpty(groupId))
throw new InvalidOperationException("Please supply a valid groupId to call #Group.");
Enqueue(new Group(userId, groupId, traits, options));
}
#endregion
#region Track
/// <summary>
/// Whenever a user triggers an event on your site, you’ll want to track it.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. </param>
///
/// <param name="eventName">The event name you are tracking. It is recommended
/// that it is in human readable form. For example, "Bought T-Shirt"
/// or "Started an exercise"</param>
///
public void Track(string userId, string eventName)
{
Track(userId, eventName, null, null);
}
/// <summary>
/// Whenever a user triggers an event on your site, you’ll want to track it.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. </param>
///
/// <param name="eventName">The event name you are tracking. It is recommended
/// that it is in human readable form. For example, "Bought T-Shirt"
/// or "Started an exercise"</param>
///
/// <param name="properties"> A dictionary with items that describe the event
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
public void Track(string userId, string eventName, IDictionary<string, object> properties)
{
Track(userId, eventName, properties, null);
}
/// <summary>
/// Whenever a user triggers an event on your site, you’ll want to track it
/// so that you can analyze and segment by those events later.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="eventName">The event name you are tracking. It is recommended
/// that it is in human readable form. For example, "Bought T-Shirt"
/// or "Started an exercise"</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
///
public void Track(string userId, string eventName, Options options)
{
Track(userId, eventName, null, options);
}
/// <summary>
/// Whenever a user triggers an event on your site, you’ll want to track it
/// so that you can analyze and segment by those events later.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="eventName">The event name you are tracking. It is recommended
/// that it is in human readable form. For example, "Bought T-Shirt"
/// or "Started an exercise"</param>
///
/// <param name="properties"> A dictionary with items that describe the event
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
///
public void Track(string userId, string eventName, IDictionary<string, object> properties, Options options)
{
if (String.IsNullOrEmpty(userId) && !HasAnonymousId(options))
throw new InvalidOperationException("Please supply a valid userId or anonymousId to call #Track.");
if (String.IsNullOrEmpty(eventName))
throw new InvalidOperationException("Please supply a valid event to call #Track.");
Enqueue(new Track(userId, eventName, properties, options));
}
#endregion
#region Alias
/// <summary>
/// Aliases an anonymous user into an identified user.
/// </summary>
///
/// <param name="previousId">The anonymous user's id before they are logged in.</param>
///
/// <param name="userId">the identified user's id after they're logged in.</param>
///
public void Alias(string previousId, string userId)
{
Alias(previousId, userId, null);
}
/// <summary>
/// Aliases an anonymous user into an identified user.
/// </summary>
///
/// <param name="previousId">The anonymous user's id before they are logged in.</param>
///
/// <param name="userId">the identified user's id after they're logged in.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Alias(string previousId, string userId, Options options)
{
if (String.IsNullOrEmpty(previousId))
throw new InvalidOperationException("Please supply a valid 'previousId' to Alias.");
if (String.IsNullOrEmpty(userId))
throw new InvalidOperationException("Please supply a valid 'userId' to Alias.");
Enqueue(new Alias(previousId, userId, options));
}
#endregion
#region Page
/// <summary>
/// The `page` method let your record whenever a user sees a webpage on
/// your website, and attach a `name`, `category` or `properties` to the webpage load.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the webpage, like "Signup", "Login"</param>
///
public void Page(string userId, string name)
{
Page (userId, name, null, null, null);
}
/// <summary>
/// The `page` method let your record whenever a user sees a webpage on
/// your website, and attach a `name`, `category` or `properties` to the webpage load.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the webpage, like "Signup", "Login"</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Page(string userId, string name, Options options)
{
Page (userId, name, null, null, options);
}
/// <summary>
/// The `page` method let your record whenever a user sees a webpage on
/// your website, and attach a `name`, `category` or `properties` to the webpage load.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the webpage, like "Signup", "Login"</param>
///
/// <param name="category">The (optional) category of the webpage, like "Authentication", "Sports"</param>
///
public void Page(string userId, string name, string category)
{
Page (userId, name, category, null, null);
}
/// <summary>
/// The `page` method let your record whenever a user sees a webpage on
/// your website, and attach a `name`, `category` or `properties` to the webpage load.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the webpage, like "Signup", "Login"</param>
///
/// <param name="properties"> A dictionary with items that describe the page
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
public void Page(string userId, string name, IDictionary<string, object> properties)
{
Page (userId, name, null, properties, null);
}
/// <summary>
/// The `page` method let your record whenever a user sees a webpage on
/// your website, and attach a `name`, `category` or `properties` to the webpage load.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the webpage, like "Signup", "Login"</param>
///
/// <param name="properties"> A dictionary with items that describe the page
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Page(string userId, string name, IDictionary<string, object> properties, Options options)
{
Page (userId, name, null, properties, options);
}
/// <summary>
/// The `page` method let your record whenever a user sees a webpage on
/// your website, and attach a `name`, `category` or `properties` to the webpage load.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the webpage, like "Signup", "Login"</param>
///
/// <param name="category">The (optional) category of the mobile screen, like "Authentication", "Sports"</param>
///
/// <param name="properties"> A dictionary with items that describe the page
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Page(string userId, string name, string category, IDictionary<string, object> properties, Options options)
{
if (String.IsNullOrEmpty(userId) && !HasAnonymousId(options))
throw new InvalidOperationException("Please supply a valid userId or anonymousId to call #Page.");
if (String.IsNullOrEmpty(name))
throw new InvalidOperationException("Please supply a valid name to call #Page.");
Enqueue(new Page(userId, name, category, properties, options));
}
#endregion
#region Screen
/// <summary>
/// The `screen` method let your record whenever a user sees a mobile screen on
/// your mobile app, and attach a `name`, `category` or `properties` to the screen.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the mobile screen, like "Signup", "Login"</param>
///
public void Screen(string userId, string name)
{
Screen (userId, name, null, null, null);
}
/// <summary>
/// The `screen` method let your record whenever a user sees a mobile screen on
/// your mobile app, and attach a `name`, `category` or `properties` to the screen.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the mobile screen, like "Signup", "Login"</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Screen(string userId, string name, Options options)
{
Screen (userId, name, null, null, options);
}
/// <summary>
/// The `screen` method let your record whenever a user sees a mobile screen on
/// your mobile app, and attach a `name`, `category` or `properties` to the screen.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the mobile screen, like "Signup", "Login"</param>
///
/// <param name="category">The (optional) category of the mobile screen, like "Authentication", "Sports"</param>
///
public void Screen(string userId, string name, string category)
{
Screen (userId, name, category, null, null);
}
/// <summary>
/// The `screen` method let your record whenever a user sees a mobile screen on
/// your mobile app, and attach a `name`, `category` or `properties` to the screen.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the mobile screen, like "Signup", "Login"</param>
///
/// <param name="properties"> A dictionary with items that describe the screen
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
public void Screen(string userId, string name, IDictionary<string, object> properties)
{
Screen (userId, name, null, properties, null);
}
/// <summary>
/// The `screen` method let your record whenever a user sees a mobile screen on
/// your mobile app, and attach a `name`, `category` or `properties` to the screen.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the mobile screen, like "Signup", "Login"</param>
///
/// <param name="properties"> A dictionary with items that describe the screen
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Screen(string userId, string name, IDictionary<string, object> properties, Options options)
{
Screen (userId, name, null, properties, options);
}
/// <summary>
/// The `screen` method let your record whenever a user sees a mobile screen on
/// your mobile app, and attach a `name`, `category` or `properties` to the screen.
/// </summary>
///
/// <param name="userId">The visitor's identifier after they log in, or you know
/// who they are. By
/// explicitly identifying a user, you tie all of their actions to their identity.
/// This makes it possible for you to run things like segment-based email campaigns.</param>
///
/// <param name="name">The name of the mobile screen, like "Signup", "Login"</param>
///
/// <param name="category">The (optional) category of the mobile screen, like "Authentication", "Sports"</param>
///
/// <param name="properties"> A dictionary with items that describe the screen
/// in more detail. This argument is optional, but highly recommended —
/// you’ll find these properties extremely useful later.</param>
///
/// <param name="options">Options allowing you to set timestamp, anonymousId, target integrations,
/// and the context of th emessage.</param>
///
public void Screen(string userId, string name, string category, IDictionary<string, object> properties, Options options)
{
if (String.IsNullOrEmpty(userId) && !HasAnonymousId(options))
throw new InvalidOperationException("Please supply a valid userId or anonymousId to call #Screen.");
if (String.IsNullOrEmpty(name))
throw new InvalidOperationException("Please supply a valid name to call #Screen.");
Enqueue(new Screen(userId, name, category, properties, options));
}
#endregion
#region Other
/// <summary>
/// Blocks until all messages are flushed
/// </summary>
public void Flush()
{
_flushHandler.Flush();
}
/// <summary>
/// Disposes of the flushing thread and the message queue. Note, this does not call Flush() first.
/// </summary>
/// <remarks>Call <see cref="Dispose"/> when you are finished using the <see cref="Segment.Client"/>. The
/// <see cref="Dispose"/> method leaves the <see cref="Segment.Client"/> in an unusable state. After calling
/// <see cref="Dispose"/>, you must release all references to the <see cref="Segment.Client"/> so the garbage
/// collector can reclaim the memory that the <see cref="Segment.Client"/> was occupying.</remarks>
public void Dispose()
{
_flushHandler.Dispose();
}
#endregion
#endregion
#region Private Methods
private void Enqueue(BaseAction action)
{
_flushHandler.Process(action).GetAwaiter().GetResult();
this.Statistics.Submitted = Statistics.Increment(this.Statistics.Submitted);
}
#endregion
#region Event API
internal void RaiseSuccess(BaseAction action)
{
if (Succeeded != null) Succeeded(action);
}
internal void RaiseFailure(BaseAction action, System.Exception e)
{
if (Failed != null) Failed(action, e);
}
/// <summary>
/// Determines whether an anonymous identifier is defined in the specified options.
/// </summary>
/// <returns><c>true</c> if the specified options have an anonymous identifier; otherwise, <c>false</c>.</returns>
/// <param name="options">Options.</param>
internal static bool HasAnonymousId(Options options)
{
return options != null && !String.IsNullOrEmpty(options.AnonymousId);
}
#endregion
}
}