Repeats and stable identifiers
Delivery is at least once and in sequence order. In practice the same event can reach you more than once, for example when a replay after a resume overlaps with events you already processed. Your program should handle that.
Ignore a repeated event
Every event has an id in d. The same event always carries the same d.id, whichever connection delivers it. Keep the ids you have handled and skip any that you see again. You only need to remember as many as one resume could replay, since events are kept for 24 hours.
The sequence number s is for ordering and for resuming. Use d.id for deduplication.
Telling opportunities apart
d.opportunity.id identifies the opportunity. It stays the same when an opportunity is hidden and later shown again.
It is not guaranteed forever. If an opportunity is deleted outright and then added again from its source, it gets a new id, and none of the other fields is a guaranteed key. In that case, compare the employer, the title and the closing date to decide whether two events describe the same role.