Candidate of the Party Democratic Party (PDP) in the February 23 presidential election, Atiku Abubakar, and his party, PDP, on Friday, finally closed their case in the petition against the victory of President Muhammadu Buhari.
Atiku and the PDP are challenging the Independent National Electoral Commission’s declaration of Buhari as winner of the February 23 presidential election at the Presidential Election Petition Tribunal.
The petitioners are asking the tribunal to nullify the victory of Buhari on grounds of alleged Irregularities, substantial non compliance with the electoral laws, widespread violence amongst others.
The petitioners are also asking the tribunal to declare them winner of the election based on the results obtained from INEC central server, which, according to them, revealed they scored majority of the lawful votes cast at the poll.
Though the petitioners had planned to call about 400 witnesses within the 10 days allotted to them to substantiate their claims, they were however able to call 62 witnesses and tendered over 50,000 documents to prove their case of alleged rigging over voting, non compliance with the electoral guidelines.
The petitioners had commenced their legal fireworks against Buhari’s reelection by calling witnesses from Niger, Kano, Kaduna, Katsina and Jigawa States amongst others wherein they alleged the electoral malpractices held sway.
Other states the petitioners are challenging Buhari’s victory include Borno, Kebbi, Bauchi, Kogi and Nasarawa where the petitioners’ witness attested to intimidation harrasment, threat to agents of Atiku and the PDP during the presidential poll.
Among the 62 witnesses called are a foreign Information, Communication and Technology ICT) expert from Kenya, David Ayu Nyango, and a local data analyst, Joseph Gbenga, to buttress testimonies of their agents at the unit, wards, local government and State levels of the alleged abnormalities during the conduct of the presidential poll, which according to the petitioners’ last witness, Osita Chidoka, is the costliest election ever conducted by Nigeria.
Chidoka, who was the National Collation agent for the petitioners and Head of the PDP situation room told the tribunal that he refused to sign the result of the presidential election because of wrong entries through the manual system.
He insisted that results were transmitted into INEC server and that INEC chairman, Prof Mahmoud Yakubu confirmed the existence of a central server in a conversation with the national agents.
Earlier, the foreign ICT expert in his evidence alleged iNEC had four websites from which he was able to generate information used in his analysis in his report to the petitioners.
He listed www.factsdontlie.com, whoistool as some of the website he said though does not belong to INEC but the information therein were uploaded by an INEC official who is anonymous.
He said if authorized by the INEC chairman he can access the server and provide them with the name and number of the server.
The witness said that the information contained in the report of his analysis were extracts from three of the four websites.
The witness confirmed that “Fact.Com was created on March 12, 2019 while the election was held February 23, 2019.”
On his part, Joseph Gbenga, the local data analyst said that he analysed forms EC8A, EC8B and EC8C in 11 focal states of the federation on the instruction of the petitioners.
Among the last set of documents tendered by the petitioners, were INEC 2019 presidential election declaration results, report on all PVC used for the presidential election, record of card reader accreditation, summary of registered voters in polling units were election were cancelled, summary of Collation at the national level and 36 copies of summary of results collation at the states level.
Meanwhile, the tribunal has adjourned further hearing till July 29, for INEC to open its defence.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature